Selected work
Systems built for messy reality.
Five systems across five disciplines. Each one starts with the problem and ends with what happens when it breaks, because that is the part that decides whether a system is still running a year later.
-
01
Automation & Operations
Client onboarding and document automation
A professional services firm was moving client intake, documents, tasks and customer updates between Slack, email, WhatsApp, Google Workspace and Trello by hand. I designed and built the whole system on n8n Cloud, including the reliability layer under it and the handover documentation. Onboarding now runs as one tracked process, with the history migrated into it rather than left beside it.
n8n Cloud · Slack · WhatsApp · Google Drive · Trello -
02
AI Engineering
VoiceInbox
Voice notes are the least searchable thing anybody sends, and the usual fix is to upload somebody’s audio to a service. I built a desktop app that transcribes on the machine the audio is already on. The model runs locally, no audio leaves the device, and the one API key it holds lives in the system keychain rather than in a config file.
Tauri · Rust · React -
03
Platform & Reliability
Platform and reliability: an experience snapshot
Not a case study, and it says so on the page. Between 2021 and 2024 I was VP of DevOps for an interactive video and live-streaming platform and owned its hybrid infrastructure, delivery and observability. It is here because it is where the reliability discipline in everything above came from.
Cloud & hybrid architecture · 24/7 production operations -
04
Enterprise Digital Systems
Controlled technical documentation in SharePoint
A team needed technical documents classified, controlled and retrievable, without a custom application becoming the only way to reach the files. I did discovery, architecture, the SharePoint configuration, the custom development and the documentation. The native library stayed the source of truth and the custom search layer reads it.
SharePoint Online · SPFx · React · TypeScript -
05
Digital Product / Web
A multilingual site built as part of the practice
MaliMake needed a site that works in four languages without four sites to keep in step, and a short path from arriving to getting in touch. I designed it, built it and structured the content and the route through it. Every technical claim on that case study can be checked against the live site.
Information architecture · Multilingual & localisation architecture
Lab
Smaller things I have built. Not every useful piece of work is a case study.
A wording policy that runs in CI
A wellness app cannot legally make medical claims, so its wording policy is a linter rather than a review somebody remembers to do: a forbidden phrase blocks the build. Beside it sits a self-test whose fixture must exit non-zero, which is how the check is proved capable of failing at all.
CI · Policy as codeSlack to WhatsApp bridge
A self-hosted bridge that carries messages between a Slack workspace and WhatsApp, supervised by a watchdog that restarts it and, since it once stayed silent through a two-day outage, escalates by email after three fast restarts while it keeps slow-restarting hourly.
Self-hosted · WatchdogStart with what exists
Which of these is closest to your problem?
Tell me what exists today and where the hard part is. I will tell you which of these it resembles and what I would look at first.
Send Dan a message on WhatsApp (opens in a new tab)or email dan@burdetsky.xyz