How the
partnership
works.

Every engagement runs the same way: a 20-minute call, then a shared queue you can add to at any time. We work through it in your priority order for a flat $2,800 a month, with a first delivery usually inside 3 working days. There are no statements of work, no change orders and no minimum term.

First call
20 min
First delivery
3 days
Monthly
$2,800
Statements of work
Zero

01 / The principle

We don’t just build software. We partner to create it.

Most teams don’t need a vendor. They need a technical partner who helps design, build and evolve a system that actually supports the business.

Build together. Own outcomes.

02 / The process

Five steps. The last one is the one that matters.

Numbered because it genuinely is a sequence — your queue cannot open before the first call, and nothing gets reviewed before it is built. Most engagements are past step three inside a week.

  1. 01

    The first call

    Twenty minutes. You describe what you are trying to build and what is currently in the way. We tell you plainly whether we are the right partner for it, including when we are not. No pitch deck, no discovery phase, no invoice for the conversation.

  2. 02

    Your queue opens

    You get a shared board and add whatever you need, however you like — a paragraph, a screenshot, a voice note. There is no request template and no ticket format to learn. Turning a business problem into a technical one is our job, not yours.

  3. 03

    We build

    We work the queue in whatever order you set, and you can reorder it any time priorities move. First delivery is usually within 3 working days. You see progress in a live environment, not in a status report.

  4. 04

    You review, we revise

    Send it back as many times as it takes. Revisions are not a separate request, do not go to the back of the queue and are never billed. A thing is done when you say it is done.

  5. 05

    We stay in it

    Launch is not the end of the engagement. We keep shipping, keep advising, and keep the context about your product in our heads instead of handing you a repository and disappearing. That is the part that makes it a partnership.

03 / What we build

Mission-critical software, not marketing sites.

The work is the system your business actually runs on: design, build, integrations and deployment. If a request falls outside this we say so before starting, never after.

Commercial SaaS products

Software you sell. Multi-tenant, billing, permissions, the parts that are tedious to get right and expensive to get wrong.

Internal platforms

The operating system for your business. The tool your team lives in all day and that no off-the-shelf product quite fits.

Backend architecture and integrations

Secure APIs, robust backend logic, and the connective work that makes separate systems behave like one.

Product design and UX

Interface and flow designed alongside the build rather than thrown over a wall to it, so what ships is what was drawn.

04 / The stack

We pick the stack that fits the problem.

We pick the stack that fits the problem rather than bending the problem to fit a stack. Sometimes the right answer is a fully custom build; sometimes it is a rapid-build platform that gets you live in a fortnight. We will tell you which one you are looking at, and why, before anyone writes code.

Frontend

  • React
  • Next.js
  • Vue
  • Nuxt
  • Svelte
  • TypeScript
  • Tailwind CSS
  • Astro

Backend

  • Node.js
  • Python
  • Go
  • Ruby on Rails
  • Laravel
  • .NET
  • GraphQL
  • REST APIs

Mobile

  • React Native
  • Flutter
  • Swift
  • Kotlin

Data

  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Supabase
  • Firebase

Cloud & infrastructure

  • AWS
  • Google Cloud
  • Azure
  • Cloudflare
  • Vercel
  • Docker
  • Kubernetes
  • CI/CD

Rapid build

  • Xano
  • WeWeb
  • Webflow
  • Bubble
  • Retool
  • Zapier
  • Make

AI

  • OpenAI
  • Anthropic
  • RAG pipelines
  • Vector databases
  • Model integration

Not seeing yours? Ask on the call. If it is not something we should be taking on, we will say so rather than learn it on your budget.

05 / Two shapes

Two ways this tends to run. Same price either way.

These describe how the relationship is shaped, not what it costs. There is one plan at $2,800 a month and neither of these changes it.

Build to partner

You have something specific to get built. We build it, launch it, and then stay on to improve and evolve it. Most partnerships start here.

Embedded product partner

You are building core software or a SaaS product and need engineering alongside you continuously — shipping, iterating and advising over time rather than delivering against a scope.

06 / Fit

We are not right for everyone, and we would rather say so now.

Working this out on the first call costs both of us twenty minutes. Working it out three months in costs a great deal more.

This is a fit if

  • You are building software that is central to the business, not a side project.
  • You want a technical partner rather than a ticket-based dev shop.
  • You care about long-term maintainability and scale, not just this quarter.
  • You can review work as it lands and make decisions.

This is not a fit if

  • You want a quick handoff and for us to disappear.
  • You are shopping purely on hourly rate.
  • You need a short-lived prototype with no future.
  • You need someone to take the blame rather than take the work.

07 / Questions

Questions about the process.

Questions about price, ownership and what is not included are answered on the main FAQ.

How quickly can we start?

Usually the same week as the first call. There is no onboarding project, no discovery phase and no statement of work to negotiate — your queue opens and the first delivery is typically within 3 working days.

How do I submit a request?

However is fastest for you. A paragraph, a screenshot with arrows on it, a voice note, a Loom. There is no template and no required format. If a request is ambiguous we ask rather than guess.

What happens if I do not like what you build?

You send it back. Revisions are unlimited, are not treated as new requests, do not go to the back of the queue and are never billed separately. Work is finished when you say it is finished.

Do you work with our existing codebase?

Yes. We work in your repositories and your accounts from day one, whether that is something we built or something you already have. Nothing needs migrating if you stop.

What happens after launch?

We stay involved. That is the difference between a partner and a supplier — we keep shipping and advising, and we hold the context about your product rather than rebuilding it at the start of each new engagement.

Twenty minutes, and you will know if this fits.

No pitch deck and no discovery phase. Tell us what you are trying to ship, and we will tell you plainly whether we are the right partner for it at $2,800 a month — including when we are not.

Book a 20-minute call