Services · 05
Digital Systems & Product Engineering. Not a brochure that looks finished.
Websites, internal tools and portals built as part of the business behind them, and handed over so somebody else can run them.
This is the supporting practice rather than the headline one. It is here because a business system usually needs a surface, and a surface built by somebody who also builds the system behind it is a different object from one built to a screenshot.
This page is about the surface. If what you need is a feature inside software that already runs, or an application where no product fits, that is Software Development & Feature Engineering and it is a practice of its own.
What is included
Eight things, and two of them happen after launch.
- 01 Information architecture and content structure INCLUDED
- 02 Custom visual direction INCLUDED
- 03 Responsive development INCLUDED
- 04 Performance and accessibility INCLUDED
- 05 SEO foundations INCLUDED
- 06 Multilingual and localisation structure INCLUDED
- 07 Owner-controlled hosting and handover INCLUDED
- 08 Technical consulting for the systems behind it INCLUDED
I also build and advise on SharePoint and other internal systems where the work spans teams, technical constraints and business requirements.
The proof
Two builds, two different problems.
Controlled documentation in SharePoint
A native library as the source of truth with a custom guided-search layer over it, and a native path to the files if the custom layer is ever unavailable.
SharePoint Online · SPFx · React · TypeScriptA multilingual site built as part of the practice
Four locales from one build, with every technical claim on the case study checkable against the live site.
Information architecture · Multilingual & localisation architectureHands-on
The site you are reading is one of them.
Static HTML, no framework, no client-side JavaScript, no cookies and no third-party request. Every claim on it is checkable from your own browser in about ninety seconds, which is the only reason it is worth writing down.
What next
Scope, then a fixed number.
Most first projects fall between a two-week scoped build and a two-month one. The number is fixed against a written scope after a discovery call, so you approve it before anything is built. What moves it inside that range, in full.
The front of the business
Does the site match the business behind it?
Tell me what the site or the internal tool has to do that it currently does not. I will tell you what I would change first and roughly what shape the work takes.
Send Dan a message on WhatsApp (opens in a new tab)or email dan@burdetsky.xyz