Services
Four kinds of work, one way of working.
Everything below ships as a self-contained file: plain HTML, CSS and JavaScript, no frameworks, no build step, no external requests. It runs from a web address, from a USB stick, or from an email attachment, and it keeps running when nobody is paying anybody a monthly fee.
Service 01
Custom interactive tools
A calculator, tracker, quiz, planner, dashboard or intake form built for one business and its actual arithmetic — not a generic template with your logo on it.
What this looks like in practice
- A quote estimator that prices a job the way you price it, so enquiries arrive already qualified
- An intake or triage form that produces a formatted summary in your inbox instead of a database you have to log into
- A client-facing tracker — symptoms, training, spending, progress — that stores everything on the client's own device
- An eligibility or "which option suits you" quiz that ends in a recommendation and a next step
- A dashboard that turns a spreadsheet you already maintain into something a customer can read
- A session planner, dosage log or scoring tool that replaces a laminated sheet
Why single-file matters here
Tools like these usually die for administrative reasons, not technical ones — a plugin stops being maintained, a platform triples its price, an agency stops answering email. A single file with no dependencies has none of those failure modes.
It also removes an entire class of legal and security problem. If the data never leaves the user's device, there is no database to breach, no processor agreement to sign, and usually nothing to disclose.
See a working exampleService 02
Party games & event experiences
A custom escape room, murder mystery or party game written around your people, your venue and your in-jokes — playable on the phones and laptops everyone already brought.
What you can commission
- An escape room for a wedding welcome party, a birthday, a hen or stag night, or a company away-day
- A murder mystery with your guests as the cast, sized to the number of people actually coming
- A team game for an onboarding day or an office party, with your company's own history as the puzzle material
- A treasure hunt or trail tied to a real building or a real route
Why this is quick to commission
Three engines already exist and are proven in shipped products: the escape-room engine, the case-file engine and the party-game engine. The three published escape rooms run on code that is byte-for-byte identical below the content — the room is data, the machinery is shared.
So a commission is puzzle design and writing, with the countdown, the answer checking, the hint ladder, the printable pack and the facilitator screen already built and already tested.
Play a two-puzzle tasterOne thing worth knowing
A game is only as good as the material it is built from. The questionnaire that starts a game commission asks for two sentences per answer, not three words, because "his cooking, the dog, Italy" cannot become a puzzle and "he burnt the lasagne at his own engagement party and we have photographs" can.
Service 03
One-page business sites
A single page that says what you do, proves you are real, and makes it easy to contact you. Fast, accessible, free to host, and owned outright.
The honest positioning
One-page sites are a crowded market and there is no point pretending otherwise. There are cheaper options and there are drag-and-drop builders that get you online this afternoon. Here is the actual difference:
- No monthly fee, ever. Hosting on Netlify, Cloudflare Pages or GitHub Pages costs nothing at this size, and the site is a folder of files, not a subscription.
- No lock-in. Builder sites are hostages. A folder of HTML moves to any host, or to any other developer, in about ten minutes.
- Genuinely fast. No page builder, no theme framework, no thirty tracking scripts. It loads before a builder site has finished deciding which fonts to fetch.
- Accessible on purpose. Real headings, keyboard navigation, visible focus, alt text and contrast that passes — because a proportion of your customers need it and the rest benefit from it.
What is included
- One page, with as many sections as the content justifies
- Light and dark, and a layout that works from a 390-pixel phone up
- Copy edited for clarity — or written from scratch, if you would rather
- A contact route that does not require a form service
- The source files, plus a plain-English note on how to change the text yourself
- Setup on free hosting, and pointing your domain at it if you have one
This site is an example of the kind of thing: four pages, three playable demos, no external requests, no cookies, no analytics.
Service 04
Digital products for other sellers
Interactive products built for your shop, sold under your name. If you already sell templates, printables or planners, this is the listing your competitors cannot copy by exporting a PDF.
How it works
- You choose an existing product to re-theme, or commission something new
- Your palette, typography, icon set, example content and shop name go into the file
- You get the product, a buyer-facing setup guide you can rebrand, and the source
- Licensing is agreed in writing first: exclusive to you, or non-exclusive at a lower price
What actually sells
Most "interactive" listings in template shops are static PDFs or design-tool templates. A product that saves what the buyer types, works offline and needs no account is a different category of listing, and it can be described in a way a printable cannot match.
The catalog on the work page is largely re-themes of shared engines, so the practice being sold here is the practice already in use.
Not only for shops — tools you give your own clients
The same arrangement works for a service business that wants something branded to hand out. A wedding planner gives a couple a seating chart with the planner's name on it; a fitness coach gives a client a training log; an accountant gives a small business a year-end checklist. The client gets something useful, and it is the person who gave it to them whose name is on every printed page.
Three working examples, branded for an invented planning studio and labeled as invented throughout: guest list & seating, wedding-day timeline and client style questionnaire. Because the branding is one block of text at the top of each file, a set of three costs appreciably less than three separate commissions — and exclusivity inside your own market is a licensing term that can be agreed with it.
Money
How pricing works
No hourly rate, no estimate that grows, no invoice you did not expect. One number, agreed before anything is built.
-
Describe the job in writing
An email or a filled-in brief is enough. If the idea is still vague, that is fine — the first reply will be questions, and those are free.
-
You get a fixed price, a delivery date and a scope list
The scope list is the important document. It says exactly what the thing will do, which means it also says what it will not do, so nobody is guessing later.
-
Half up front, half on delivery
The first half books the time. The second is due when the finished file is in your hands and does what the scope list says.
-
Changes are re-quoted, never back-billed
A round of revisions inside the agreed scope is included — you look at the finished tool, sit with it, and send one consolidated list. However many items are on it. If the scope itself grows, you get a new fixed price for the addition before any of it is built.
What moves the price up
- More distinct screens or modules
- Real arithmetic — schedules, projections, scoring, anything with rules that interact
- A lot of original writing (a game is mostly writing)
- Printable output, which is a second layout with its own rules
- A hard external deadline that displaces other work
What brings it down
- A clear brief with real examples of the inputs and outputs
- Re-theming something that already exists rather than starting new
- Fewer options — one confident default beats five configurable ones
- Supplying your own copy, or being happy with plain copy
- Flexible timing
What you own when it is done
The delivered file and its source, outright, with no license to renew and no account to keep alive. Host it, copy it, sell it, edit it, or hand it to another developer. Two weeks after delivery are covered for anything that does not behave as the scope list says it will.
Method
How the work gets done
There is no mystery to it, and no secret sauce worth pretending about. The value is in the testing and the scoping, not in the typing.
Plain code, on purpose
HTML, CSS and JavaScript. No framework, no package manager, no build step. Nothing in the file has a version number that can go stale, which is why these keep working years later without maintenance.
Verified in a real browser, not just written
Every build is opened in an actual browser and driven end to end before delivery: every control clicked, every error path triggered, phone width and desktop width, light theme and dark, keyboard-only as well as mouse. Screens are looked at, not just rendered.
The scope list is the contract
Most disappointing software projects are scoping failures, not coding failures. Writing down what the thing does before building it is the single cheapest way to avoid that, so it happens first, in writing, every time.
Honesty
What this is not right for
Sending the wrong job away costs a lot less than taking it.
Anything needing accounts
User logins, roles, permissions, password resets. That needs a server and a database, and therefore a monthly bill and somebody on call. Different kind of project, and not this one.
Payments and inventory
Taking card payments, managing stock, syncing orders. Shopify and its equivalents do this properly and cheaply. Use them.
Native mobile apps
App Store and Play Store builds mean two codebases, review queues and annual developer fees. A web app that works offline covers most of the reasons people ask for one.
Multi-user, real-time anything
Shared documents, live collaboration, chat. All of it needs a server that is always running, which is the exact thing this approach removes.
Big content sites
Hundreds of pages, a blog with several authors, a content team that needs an admin area. A content management system is the right answer there.
Rescuing a large legacy codebase
Inheriting somebody else's half-finished platform is a specialism, and it is not this one. Small, whole, finished things are.
Questions that come up
Practical answers
- Can it collect data and send it to me?
- Yes, in two ways that do not need a server. It can build a formatted summary the user copies or opens in their own email app, or it can post to a form service you already pay for. If you genuinely need a database, that is a bigger project and you will be told so rather than sold a workaround.
- Can I edit it myself afterwards?
- The parts you are most likely to want to change — text, prices, colors, options — are grouped at the top of the file with plain-English comments around them. Everything else is yours to change too, but that part is written to be changed by hand.
- Does it work on phones?
- Yes, and that is tested rather than assumed. Layouts are checked down to 390 pixels wide, which is a standard modern phone, and everything is usable with a thumb.
- What about accessibility?
- Semantic HTML, keyboard navigation with visible focus, alt text on every image, and color contrast that passes WCAG AA. If you have a specific compliance requirement, say so in the brief and it goes in the scope list.
- Can you host it for me?
- Setup on free hosting is included, and you own the account so nothing is hostage to this studio continuing to exist. Pointing an existing domain at it is included too.
- What if it breaks?
- Two weeks after delivery are covered for anything that does not behave as specified. After that, fixes are quoted like any other job — but with no dependencies to rot, there is very little that can break on its own.
- Do you sign NDAs?
- Yes. Send it with the brief.
Ready when you are
Send a paragraph about the job. The reply will be either a fixed price and a date, some questions, or a straight recommendation to do it a different way.