The engineering team behind firms that sell expertise, not software
We build the websites, applications, data and AI that studios, agencies and advisory firms put their name to. Our published work here is a partnership: woodfrog is the engineering team behind Design Asylum Studio, with ten-plus projects shipped together since 2025 and a typical build going from approved design to production in two months.
- Published work in this industry
- 1 customer story
- Projects shipped with Design Asylum
- 10+
- Approved design to production
- 2 months
- Developers the studio had to hire
- 0
On this pageWhat we hear in professional services
What we hear in professional services
Each of these comes from our Design Asylum partnership or from an article we wrote for services firms.
- 01The design has to ship as designed
Handovers between a design team and an outside developer are where fidelity, motion and detail get lost.
- 02No engineering bench of your own
Keeping engineers on staff for work that arrives in waves is expensive and slow to scale, and hiring for every stack a client uses is not your business.
- 03Every client brings a different stack
Web, mobile, cloud and enterprise software, each with its own integrations, data and, increasingly, AI features the client wants inside the product.
- 04The process lives in one person's head
Invoice coding takes two days a week, and what happens in those two days is a person, a shared drive and a spreadsheet tab called temp.
- 05The workflow waits four days on one approval
It runs in a second and then stalls on the person who is on leave. The fix is an age, a queue, a deputy and a stated default.
- 06Not everything needs a model
A model earns its place on three conditions. A great deal of what gets scoped as an AI project fails all three, and a form, a rule and a lookup would do it better.
What we have delivered
One published customer story, named.
Since 2025, across web, applications and AI.
Because engineering is in the room from the brief.
A woodfrog pod of three, working with the studio as one team.
woodfrog is the studio's engineering team.
Read the full account
- Customer storyThe engineering partner behind a design studio, ten projects in
The studio owns brand, research and UX/UI. woodfrog owns the build, the data and the AI.
Read the Design Asylum story ↗
Where to start
Four places a first engagement can begin. Week 1 tells you which one comes first.
- ApplicationsWebsites and apps, built to the design
The system your team, or your client's, works in all day.
Applications and automation ↗ - ApplicationsOff paper, WhatsApp and one shared spreadsheet
The process written down first, then moved into a system with an owner on every step.
Process digitisation ↗ - AIAI features inside client products
One agent on live data, with a kill switch, built directly on Claude.
AI agents ↗ - AIFind out what is worth building
One week, and you know which two or three AI initiatives are worth building, and which are not.
AI audit and roadmap ↗
How the first weeks run
The same three phases in every industry. What changes is what we build in them.
- Week 1, fixed feeAudit
Two calls and a written one-pager. Yours to keep whether or not you continue.
- Weeks 2 to 6Build
Something real in front of real users by week three. Median six weeks to the first production-grade artefact.
- Week 7 onwardOperate
Quarterly reviews and on-call governance. The people who built it pick up the phone.
Questions we get asked
Further reading
- You cannot automate a process nobody has written downThe flowchart you were handed describes the good day.
- Most of the work you want to automate does not need a modelA model earns its place on three conditions.
- Automation stalls at the human step, so design for the person on leaveAn age, a queue, a deputy and a stated default.
Start with the Week 1 audit
Two calls and a written one-pager naming the first thing worth building, and who owns it. You keep it either way. NDA-friendly, fixed scope. Write to hello@woodfrog.tech.
