Services and prices
For each heading, what gets delivered, how long it takes and which budget band it sits in are written out below. What falls outside each one is written with the same weight.
What are you looking to have built?
I am looking to have a website built.
Design through deployment, one pair of hands. Fast, and findable.
Websites
Design through deployment, one pair of hands. Fast, and findable.
Typical duration · 2–4 weeks
Where a site slows down is usually decided inside the design: how many typefaces load, what size an image is cut at, which section the browser has to compute. Those get settled where design and code are decided at the same table. After delivery the structure is left simple enough for your own team to update the content, so a text change does not mean coming back.
ProofLiseUP
This service is a good fit in the following cases:
- a single, well-made landing page is required
- the current site is slow, does not work correctly on mobile, or no longer represents the brand
- a new brand needs to appear online for the first time
- visibility in search results is insufficient
The following fall outside this service:
- another site is to be copied line for line
- payment would come from a share of the revenue the work generates later
- three weeks of scope is required by the following day
- a new campaign page has to be produced by hand every week
What is delivered
- A design built around your brand: type scale, colour, components
- Built in Next.js, tested from phone width up to desktop
- Technical SEO: metadata, sitemap, structured data, speed
- A panel or a file-based setup, so the content can be edited in-house
- Deployment, plus domain and email wiring
Where a project lands in the band is set by the number of page templates, the shape and language count of the content model, and how many outside systems the site connects to: a one-template brochure site and a multilingual product catalogue sit at opposite ends of the same band.
Web applications
Sign-in, data and dashboards. An interface that runs the work rather than describing it.
Typical duration · 4–10 weeks
In an application the real work sits under the interface. Who can see which record is decided while the data model is drawn, not while the screens are; an authorisation rule added afterwards is only ever as strong as the data underneath it. Whether an action can be undone depends on the earlier state still being kept somewhere. A fault gets noticed early only where what happened was written down at the time. Apex’s bench for live race data and LiseUP’s membership and matching flow were both built in that order, data model first.
This service is a good fit in the following cases:
- the process currently runs in a spreadsheet or over WhatsApp
- users need to sign in and see only their own data
- the off-the-shelf tool in use (Notion, Airtable) has reached its limits
- an idea needs to be put in front of investors or first users
The following fall outside this service:
- an equivalent of a large platform (Instagram, a major marketplace) is to be produced within a few weeks
- a mobile application to be published on the App Store or Google Play is required
- the scope is expected to grow mid-build while the price stays fixed
What is delivered
- Data model and schema design
- Authentication, roles and authorisation
- The application interface: lists, forms, dashboards and state screens
- Server-side validation; no rule lives only in the browser
- Deployment, environment configuration and basic error tracking
What moves the price is not the number of screens but the number of distinct user roles and how many outside systems connect; a single-role internal tool sits at the bottom of the band and a multi-role dashboard pulling live data sits a long way above it.
AI agents
Systems that take over the repetitive work and log every step they take.
Typical duration · 3–8 weeks
Whether an agent is useful is decided by the boundaries drawn around it rather than by the choice of model: which records it can read, which action it can complete on its own, and who it hands the work to when it is not sure. Those boundaries are written out item by item while the workflow is mapped, so they are part of the agent’s definition rather than a control added afterwards. Anything that falls outside them goes to a person instead of quietly turning into a guess.
ProofApex
This service is a good fit in the following cases:
- a request needs to be carried from intake to close, not only answered
- the same task is done by hand every week by someone on the team
- incoming requests need to be read and routed to the right person
- there is plenty of data and nobody with time to read it
The following fall outside this service:
- a decision that cannot be undone is involved: payments, medical or legal calls
- the work leaves no margin for error and the output has to be right every single time
- the purpose is bulk messaging, fake accounts or collecting data without permission
What is delivered
- Mapping the workflow: what automates, what stays with a human
- The agent itself: tools, data access and boundaries
- A hand-off threshold, and where the hand-off lands (email, Slack, a dashboard)
- A log of every run, so any output can be traced to its source
- Integration with what you already use (Google Sheets, email, databases, APIs)
Every system the agent touches adds a line to the price, and the state of the data inside those systems decides the rest. On most jobs, putting messy data in order takes longer than building the agent itself.
Something else
Work that does not fit a category: feasibility first, then a written scope.
Typical duration · Depends on scope
Most of what gets called custom software lands here: a browser extension, a data pipeline, an internal tool, a bot, or several of those at once. On work like this, price is not the first question that gets answered. Your data and the systems you already run get looked at first, and whether the thing can be built at all is answered from that. The scope is written only afterwards. If this is not the right place for it, that is said plainly too.
ProofApex
This service is a good fit in the following cases:
- what is wanted is clear, but the work does not fit a category
- work that was started and stalled halfway needs to be taken over
- feasibility needs to be established first
The following fall outside this service:
- a free sample is requested first, to see how it would go
- it is not yet settled who decides what
What is delivered
- A short discovery: what the problem is, and what counts as done
- Scope, timeline and price in writing
- Build, delivery and handover
How the process works
- 01
First exchange
You write down what you want built, who it is for, and what you already have today. Your enquiry is answered within two business days, and where something is unclear the answer arrives with the questions attached.
- 02
The written quote
Scope, timeline and price are put in writing. Once the scope is clear the price is fixed, and the amount payable is known before any work starts.
- 03
Development
Delivery happens in stages. You see a working version at each one, so there is no screen you meet for the first time at the end.
- 04
Handover
Deployment is completed and the update procedure is handed over. The code, the domain and every account are either opened in your name or transferred to you.
The first month after delivery. For the first month after delivery, bug fixes are included in the price. That month is not a maintenance arrangement; maintenance is agreed separately and it is optional.
What the price covers. Design, development, testing, going live, setup and handover are in the price. Hosting, domain and third-party licence fees (typefaces, APIs, service subscriptions) fall outside it; those accounts are in your name, so you pay the provider directly.
Urgent work. The durations above apply to the normal run of things. If delivery is needed sooner, the work is priced separately; state the date it has to meet.
Who is on the other side. One person carries the work from start to finish, so the person who takes the job is the person who delivers it. What binds it is paperwork: a proposal, a services agreement, a non-disclosure agreement, an acceptance and handover record and a maintenance agreement are signed separately for every project. Read what each of the five settles
Common questions
What happens if the scope changes mid-build?
A new request is not quietly folded into the scope already running. What changed is written down and quoted on its own, with its own timeline, and it joins the queue once it is approved. A change that is not approved does not hold anything up; the agreed scope keeps its own schedule.
Fixed price or hourly?
There is no hourly or day rate. When the scope is not clear yet, a short discovery comes first, and what the discovery produces is a scope a fixed price can be put on. What fixed price means in practice is this: if the work takes longer than estimated, that is the studio’s problem rather than yours.
Do I own the code?
Yes. The handover is not conditional on a maintenance agreement: the repository, the domain and the accounts stay with you whether or not maintenance continues. You may move to another developer at any time, and you do not have to give a reason for it.
After delivery, what counts as support and what does not?
If something delivered does not behave the way it was described, that is a bug and it gets fixed. A new page, a new field or a new rule is not a bug, it is new work. That line is drawn in the acceptance and handover record, so it is not argued about afterwards.
Do you do the design as well?
Yes. If a design already exists, it gets built to; if not, the design is part of this work and there is no second supplier to find. Where an existing design system or brand guideline has to be followed, that goes into the scope in writing.
What do you build with?
Mostly Next.js, TypeScript and Python. What each project actually uses can be seen on the work page, and that list is not hand-written: it is derived from the projects' own declarations.
Building something?
September 2026 onwards, there is room for new work.