Services
What gets built, and what it costs.
Six things the studio does well. Most engagements combine two or three of them — because a website that quietly files enquiries into a dashboard is worth considerably more than either piece alone.
Business websites & landing pages
The site is usually the first thing a prospective customer sees and the cheapest thing to get wrong. Sites here are built as single-purpose instruments: be found, be understood in ten seconds, produce an enquiry.
- Structure & copy direction — the order information appears in, written to answer the questions people actually arrive with.
- Performance — no heavy frameworks where none are needed. Pages that load instantly on a phone, on mobile data, in a car park.
- Search visibility — semantic markup, structured data (LocalBusiness, Service, FAQ), sitemaps and metadata that Google can read without guessing.
- Measurement — analytics with GDPR-compliant consent, plus session insight so you can see where people hesitate.
- Accessibility — keyboard navigation, sensible contrast, real focus states. This is table stakes, not an upgrade.
- HTML/CSS/JS
- Next.js
- Astro
- Tailwind
- GA4 + Consent Mode
- Schema.org
- Vercel
Web applications & SaaS prototypes
When a spreadsheet stops coping, or an idea needs proving before anyone commits a year to it. These are real applications — accounts, permissions, a database, an audit trail — not clickable prototypes that fall over on contact with a customer.
- Product shaping — deciding what version one must do and, more importantly, what it must not.
- Authentication & roles — staff, managers, customers, each seeing only what they should, enforced at the database.
- Data modelling — a schema that reflects how the business actually operates, so it survives the second and third feature.
- Customer-facing surfaces — portals, tracking links, booking forms, generated PDFs.
- A path to more — built so that a prototype which works can grow, instead of being thrown away.
- Next.js
- React
- TypeScript
- Supabase / Postgres
- Row-level security
- Vite
AI-powered tools & integrations
AI where it genuinely outperforms conventional code, and nowhere else. That means reading unstructured documents, drafting text, classifying messy input and summarising — with deterministic software handling every step that has to be right every time.
- Document understanding — invoices, delivery notes, forms and PDFs turned into structured rows you can actually use.
- Drafting & summarising — first drafts of quotes, replies, reports and listings, in your voice, for a human to approve.
- Assistants over your own data — a question box that answers from your records rather than from the internet.
- Guard-rails — validation, confidence thresholds, human approval steps and a clear log of what the model did and why.
- Cost control — right-sized models, caching and batching, so the running cost is a line item rather than a surprise.
- Claude API
- Structured output
- Tool use
- Python
- Prompt caching
- Evaluation harnesses
Workflow & process automation
The unglamorous work with the fastest payback. Anything a person does the same way every week — copying between systems, chasing an update, producing an identical report — is a candidate.
- System integration — making the tools you already pay for talk to each other, rather than replacing them.
- Scheduled jobs — work that happens overnight, on the first of the month, or the moment a form is submitted.
- Notifications that matter — the right person told the right thing, by email, WhatsApp or Slack, without a daily digest nobody reads.
- Reporting — numbers assembled automatically and delivered, instead of rebuilt by hand each Monday.
- Failure handling — retries, alerts and a log, because an automation nobody trusts is worse than none.
- Python
- Node
- REST & webhooks
- Google Workspace APIs
- Cron / scheduled functions
Internal tools & dashboards
The screen your team opens first thing. Built around your process, your statuses and your vocabulary — including the untidy exceptions that generic SaaS refuses to model and your team therefore tracks on paper.
- Operational views — jobs, bookings, stock, tickets, projects: what's in progress, what's stuck, what's overdue.
- Money — quotes, invoices, payments, recurring fees and renewals, visible before they become a problem.
- Time & capacity — where the hours actually went, and whether the price was right.
- Metrics — a small number of honest charts rather than a wall of vanity numbers.
- Mobile-first where it matters — because the person updating a job is often standing next to it.
- Next.js
- TypeScript
- Supabase
- Recharts
- shadcn/ui
- Role-based access
Ongoing improvement & support
Offered where it's genuinely useful and declined where it isn't. A static brochure site rarely needs a monthly fee; a system your operations depend on usually does.
- Monitoring & uptime — knowing something broke before your customers tell you.
- Iteration — a small, agreed number of hours each month spent on the highest-value change, decided together.
- Content & campaigns — new pages, seasonal landing pages, updated pricing.
- Advice — a technical person to ask before you sign a three-year contract with a vendor.
- No lock-in — code, accounts and domains are yours from day one. Support is a service, not a hostage arrangement.
Three ways to
work together.
Every engagement starts with a fixed written scope and a fixed price. You will always know what you're buying before you commit to it.
Diagnostic
A short paid engagement to map a process, identify what's costing you time and produce a costed plan — which you're free to take elsewhere. Best when you know something is wrong but not what to build.
Fixed-scope project
The default. A defined outcome, a fixed price, a delivery date and a written list of exclusions. Staged payments, typically on start and on delivery.
Continuous partnership
An agreed block of time each month for businesses whose software keeps evolving. Rolling, cancellable, and reviewed openly every quarter.
On pricing
Prices are quoted per project, not per hour, because you're buying an outcome rather than a timesheet. A landing page and a multi-role operations platform are not the same purchase, so there is no menu price list on this page — it would be dishonest for both of us.
What you can rely on: a written figure before any work starts, no billing for the conversation that produces it, and no change to that figure unless you ask for something that wasn't in the scope — in which case you'll get a new figure to approve first.
Invoicing in GBP or EUR. International clients welcome; time zones have never been the hard part.