We also build the thing, not just the prompt.
WordPress sites, Shopify stores and SaaS products, delivered on a fixed scope with a written proposal before any work starts.
What we build
Three core lines of work, plus the support that keeps them running after launch.
WordPress websites
Marketing sites, blogs and content platforms on block themes. Custom blocks instead of page-builder bloat, editors your team can actually use, clean migrations, and performance work that shows up in Core Web Vitals.
Shopify stores
Theme builds and customisation, product and collection structure, app and payment integrations, subscription setups, and migrations from WooCommerce or a legacy cart without losing URLs or SEO equity.
SaaS and web apps
From an MVP that proves the idea to dashboards, APIs and integrations. Auth, billing, roles, background jobs and deployment pipelines included, with tests where they earn their keep.
AI features and automation
Assistants grounded in your own documentation, structured extraction from messy inputs, internal tooling, and prompt pipelines with evaluation so quality is measured rather than assumed.
Rescue and audit work
Slow sites, broken checkouts, inherited codebases with no documentation. A paid audit gives you the risk list and a straight recommendation: repair, refactor or rebuild.
Care and maintenance
Optional retainers for updates, backups, monitoring, small changes and a defined response window. Or a full handover if you would rather run it in house.
How we work
Five steps, no discovery theatre. You see working software early and often.
Scope conversation
One call or email thread to establish the outcome, the constraints, the deadline and the budget range. If we are the wrong fit, you hear it here.
Written proposal
Fixed price, deliverables, timeline, assumptions and what is explicitly out of scope. Nothing begins until you approve it in writing.
Build in weekly slices
Work lands on a staging environment every week, so you review real pages and real flows instead of status updates.
Review and QA
Cross-browser and mobile checks, accessibility pass, performance budget, content proofing, and a fix list closed out before launch.
Launch and handover
Deployment, redirects, analytics if you want it, plus documentation and a walkthrough recording so your team is not dependent on us.
Three ways to work together
- Fixed-scope projectA defined build with a fixed price and date. Best for new sites, stores and MVPs where the outcome is clear.
- Sprint blockA block of development time for a roadmap of smaller items, prioritised by you week by week.
- Care retainerOngoing updates, monitoring, backups and small changes with an agreed response window.
On pricing: every quote follows a scope conversation, because a number given before that is a guess dressed up as a price. You get a fixed figure in writing, not an open hourly meter.
What we build with
Tools are chosen to fit the job and your team, not to pad an invoice.
| Area | What we build with |
|---|---|
| WordPress | Block themes, custom blocks, ACF, WooCommerce, migrations, Core Web Vitals work |
| Shopify | Liquid themes, custom sections, app and payment integrations, catalogue migrations |
| Web apps | React or Next.js front ends, Node or Python services, PostgreSQL, REST and GraphQL APIs |
| Infrastructure | Vercel, Cloudflare, AWS, containerised deploys, CI pipelines, monitoring and backups |
| Payments and auth | Stripe or Paddle billing, subscriptions, SSO, role-based access |
| AI features | OpenAI, Gemini and Claude APIs, retrieval over your own content, evaluation harnesses |
Where this works, and where it does not
Do this 05
- You know the outcome you need, even if not the solution
- You want one accountable team, not a resource pool
- You can give feedback weekly
- You value a written scope over a rushed start
- You want to own the code and the accounts
Not this 05
- You need a full agency on retainer with 24/7 cover
- You want the cheapest possible bid
- The brief changes weekly with no re-scoping
- You need work started before anything is agreed in writing
- You are looking for guaranteed SEO rankings
Asked often, answered plainly
How does a project usually start?
Email [email protected] with what you want built, your deadline and a link to anything that exists today. You get a short scope conversation, then a written proposal with a fixed price, the deliverables and the timeline. Nothing starts before you approve that document.
Do I own the code and the design?
Yes. On final payment, ownership of the custom code, design files and content produced for you transfers to you. Third-party licences, such as a premium plugin, theme or paid API, stay under their own terms and are listed in the proposal.
Can you take over an existing site or codebase?
Often, yes. It starts with a paid audit: we read the code, list the risks, and tell you honestly whether repairing or rebuilding is the better use of your budget. You keep the audit either way, even if the answer is that you do not need us.
What about maintenance after launch?
Optional. A monthly retainer covers updates, backups, monitoring, small changes and a response window for urgent issues. If you would rather run it yourself, you get a handover document and a walkthrough recording instead.
Do you work with AI features?
Yes, and with the same scepticism you will find across this site. Useful cases include assistants grounded in your own content, structured extraction, and internal tooling. We will tell you when a feature would be cheaper and more reliable without a model in the loop.
Tell us what you are building
One email with the outcome, the deadline and any existing links is enough to get a straight answer on fit, scope and price.