How we work

From "here's how we do it today" to software your team runs every day.

You don't need a spec, a requirements document, or a fully defined project. You need to know how your business works, and you already do. Here's what happens from the first conversation through launch and after.

It starts with a conversation

The first step is a 20-minute call. Tell us what's getting in the way, in your own words: the spreadsheet everyone depends on, the order that gets typed in three times, the system that's hard to change.

We'll ask questions, and we'll tell you honestly what we think. Sometimes that's custom software. Sometimes it's connecting what you already have, improving an existing system, or leaving it alone for now. If we're not the right fit, we'll say so.

The project

Three deliberate steps, so nothing important gets skipped.

STEP 01

Map what's actually going on

We sit down with the people who do the work and follow it from start to finish: the process, the money rules, and the exceptions that only come up a few times a year. Your spreadsheets, forms, and existing systems are the first draft. By the end, we both have a clear picture we can point to.

STEP 02

Design the data and the screens

We shape the structure underneath first, because that's what keeps software reliable as it grows. Then we build the screens people use on top of it and review them with you as we go. We usually start with the piece that costs the most time, so your team gets something useful early and helps shape what comes next.

STEP 03

Deliver a system your team can run

We bring your existing data over and check it against the original, then help your team get comfortable with the new system. It's designed so your people handle day-to-day operations themselves, without waiting on us.

Your part

What we'll ask of you

You know the business. We handle the technology. These are the few things that make the biggest difference in how a project goes.

  • ✓Time with the people who do the work. The person who handles the exceptions every day often knows things nobody wrote down.
  • ✓A look at what you use today. Spreadsheets, paper forms, reports, and access to existing systems or exports, so we build from how things really work.
  • ✓Honest feedback as screens take shape. "That's not how we'd do it" is the most useful thing you can tell us, and earlier is better.
  • ✓Someone who can make decisions. When a question comes up about how the business should work, it helps to know who has the final word.

After launch

Your team runs the system day to day. Software that supports daily operations keeps changing with the business, though, so updates and maintenance still matter.

How that works depends on the way you choose to work with us. You can take the code and look after it yourself, keep us on retainer for changes and fixes, or subscribe and let us host and maintain it. Whichever you choose, the software is built so that any developer who comes after us can understand and change it.

Compare the three ways to work with us →

Start with a conversation

Tell us how it works today.

A 20-minute call, no deck and no pressure. Describe the problem in your own words; you don't need technical details or a defined project. We'll tell you honestly whether we can help and what the first step would be.