A working prototype of your idea in two weeks. NZ$5,000, fixed.

Two workshops with the senior people who would build it. You leave with a clickable prototype, a written scope and a fixed price and timeline to build it. The NZ$5,000 comes off the build if you go ahead, and you keep everything if you do not.

What you leave with. Four things, all yours.

  • A clickable prototype of the key screens, built with you over two workshops.
  • A written scope: what is in, what is out, what it connects to.
  • A fixed price and timeline to build it.
  • A straight recommendation, including "use a website builder" or "buy this product" when that is the honest answer.

The two weeks. Ten working days, two of them with you in the room.

WhenWhat happens
Day 1Workshop one. Who uses it, what it connects to, what happens when it goes wrong. We map the process with the people who do it.
Days 2 to 4Flows and wireframes of the key screens. You see them as they land, not at the end.
Day 5Workshop two. We walk the wireframes with you and the people who will use the thing, and change them on the spot.
Days 6 to 9The clickable prototype, the written scope, and the risks and integrations checked with the systems you already run.
Day 10Presentation. The prototype, the scope, a fixed price and a timeline, and our recommendation, including "a builder would do" if it is true.

What a sprint prototype looks like. Sample screens coming soon.

01

Sample 1

A customer portal: quotes, jobs and documents behind a login. Screens being prepared; ask on the call and we will walk you through a real one.

02

Sample 2

A field app: a job sheet that works offline on site. Screens being prepared; ask on the call and we will walk you through a real one.

03

Sample 3

A booking flow: availability, payment and a confirmation. Screens being prepared; ask on the call and we will walk you through a real one.

Who runs it, and what happens next.

John Halvorsen-Jones, Applicable's founder, with one designer or developer from the team that would build it. Thirty years in technology, on every project since 2008. We run 3 sprints a month.

On day ten you have a fixed price. Say yes and the build starts the following week, with the NZ$5,000 credited. Say no, or not yet, and the prototype and scope are yours to take to anyone. Seewhat the build costs and how a project runs.

Two weeks with the people who would build your project. Two workshops, a clickable prototype of the key screens, a written scope and a fixed price and timeline to build it. NZ$5,000 plus GST, credited in full against the build if you go ahead. You keep everything either way.

Because a quote from a vague brief is a guess, and guesses blow out. The sprint turns the brief into screens people can click and a scope both sides can read, so the fixed price that follows is one we will hold.

No. A brochure site with a contact form is quoted from a conversation. The sprint is for anything with logins, integrations, bookings or a workflow behind it.

Some things can be, and we say so at the sprint. A portal that talks to your accounting system and is used by your customers cannot be done well in a fortnight, and a promise that it can is a promise about the invoice, not the software. We publish weeks, not days.