Software shaped to how you work

Web apps and software products

Software products you own, from first version to production.

Talk to us about this
  1. 01How you work
  2. 02Scoped in writing
  3. 03Built and tested
  4. 04Yours to keep

When what you need is a product, for your clients or for sale, we scope it, build it and run it in production: sign-in, roles, billing, integrations and hosting. We also take over half-built products, after reading the code first.

Sound familiar?

  • We have an idea for software our clients would pay for, but no team to build it.
  • A previous developer left us with something half-built.
  • We pay for several subscriptions that each do part of the job.
  • Our prototype works in a demo and falls over with real users.

What you get

What we hand over

  1. 01Product scoping and a technical plan you can read
  2. 02Sign-in, roles and separate data for each customer
  3. 03Billing and subscriptions through your own payment account
  4. 04Integrations and APIs to the tools your customers use
  5. 05Production hosting, monitoring and a documented handover
  6. 06For takeovers: a written code review first, saying what to keep and what to replace

Works with what you run

Names only. We aren’t partners of any of them, and we start from what you already run.

  • Next.js
  • React
  • TypeScript
  • Postgres
  • Supabase
  • Convex
  • Stripe
  • Vercel

How it stays safe

Our principles, applied here

The same rules run through everything we build. How we work

  • The repository, hosting and payment accounts are yours from day one.
  • We test sign-in and the separation of each customer’s data before anyone else uses it.
  • The handover pack is written so another developer could pick it up.

Before you hire us

When you don’t need this

We’d rather say it now than after you’ve paid for it.

  • If you haven’t tested whether people want it, start smaller: a landing page, a waitlist or a manual version first.
  • If an existing product does most of it, paying for that is usually cheaper than building.

Not sure which side of the line you’re on? Take the scorecard. It’s private, and nothing is sent unless you choose to send it.

Questions

Common questions

Yes, after a written review. We keep what works and say plainly what doesn’t.

Usually Next.js, React and TypeScript on a Postgres or Convex database, with Stripe for billing. It’s the same kind of stack our own learning platform runs on.

Related

Often paired with

See all services

Tell us what you run, and what this would need to do.

Five short steps. We’ll tell you honestly whether this is the right fit.

Start a project