Skip to content
Discuss your project

Software built around how your business actually works

At some point the spreadsheets, the shared inbox and the WhatsApp groups stop scaling. That's usually when a business needs its own software: not everything at once, but the one tool that removes the daily friction.

Right for
teams that have outgrown spreadsheets and messages
Starts with
Discovery & Scope, or a written quote for a small tool
A sample approvals screen: as each release step passes, one order changes from awaiting approval to approved

What we build

Signs it's time Your operations run on spreadsheets and messages that have stopped scaling. You need a first working version of a product. Clients, partners or field staff need a portal of their own.

  • Web applications that work on any device through the browser.

  • Internal tools: order tracking, approvals, inventory, scheduling, whatever your team does by hand today.

  • Dashboards that pull numbers from the tools you already use.

    Shown here

  • Client and partner portals.

  • Admin panels and first versions of software products.

Illustration: a Postgres query that counts orders per day types itself in an editor. It becomes a bar chart of seven days with a line drawn over the bars and a tooltip on one day. Sample data, with no figures.

How we scope it

Software projects go wrong when the scope is a wish list. For larger tools we start with Discovery & Scope: who the users are, what they do today, what the first release must do, and what waits. You get a written scope, a plan and an estimate before any build. For smaller tools, that's a short conversation and a written proposal.

How Discovery & Scope works
A workflow, scoped
First release
Order inWho enters it, and from where?
ApprovedWho approves, and on what?
InvoicedFrom which data?
Waits
ReportedWho reads it, how often?

What you get, what we need

Handed over, in your name
  • designscreens and flows
  • repositorycode reviewed before it merges, in your account
  • testschecks that run before each release
  • staginga test version you can click through
  • productionhosting in accounts you own
  • docsdocumentation and handover
  • admin-accesslogins in your name, not ours
  • fix-windowafter launch; written support if you want us to keep developing it

From you

  1. One person who can make decisions.
  2. Access to the people who do the work today.
  3. Honest feedback at each milestone.

Questions

Ownership, changing scope, taking over and timelines.

Do we own the code?

Yes. On payment, the code, design and accounts are yours, as written in the agreement.

What if the scope changes during the project?

It usually does, a little. Changes are written up with their effect on time and cost, and built only after you approve them.

Can you take over software someone else built?

Often, after a review of the code and setup. We'll tell you if it's sound, fixable or better rebuilt.

Read the guide: Your developer left and you can't get into your website: what to do first

Do you build mobile apps?

We build web applications, which work on phones through the browser. We don't build native mobile apps at the moment.

Read the guide: Website, web app or mobile app: what your business should build first

How long does it take?

It depends on the first release. Discovery & Scope answers that with a plan, not a guess.

What does it cost?

It depends on what you need. Tell us about the project and we'll send a written quote with the scope, timeline and what's included.

From the Blog

Tell us what your team does by hand today.

We reply within 24 hours.

What is it about? Optional, pick any