How we thinkManifesto · values · process

We build software the way it should have been built all along.

Precise. Purposeful. Owned by you. This is the thinking behind every engagement we take — and every line of code we ship.

The manifesto

Why we exist, in plain language.

01

On the state of software for small businesses

Small and midsize firms have been sold a lie for thirty years: that enterprise software, scaled down and repriced, is what they need. Enterprise software was built for IT departments, change-management budgets, and six-month implementations. You don't have those — you have a specific bottleneck, a team that knows exactly how your firm works, and a need for software that fits around your reality, not the other way around.

02

On why AI changes the economics

For most of software's history, building truly custom software for a small firm was economically irrational. AI changes that calculus. A module that would have taken six months in 2019 ships in six weeks today — not because the quality is lower, but because AI dramatically compresses the distance between a well-defined problem and a working solution. The economics of bespoke software for smaller firms are now viable. We're building the firm that takes advantage of that window.

03

On what 'AI-native' actually means

The term gets used loosely. For us, it has a specific meaning: the intelligence is structural, not cosmetic. An AI-native module doesn't have a chatbot bolted onto a spreadsheet. The intelligence lives in the data model, the validation logic, the output format, and the decision surface. The user experience feels like the software already knows what you're trying to do — because it does.

04

On the handoff model and why we believe in it

We chose the handoff model deliberately — not because it's the most profitable structure for us, but because it's the most honest one for clients. A subscription-based development firm has a structural incentive to keep you dependent. We don't want that incentive. We want the incentive that comes from building something so good you tell other firms about it. That's the only growth model we're interested in.

Core values

Six principles that govern every engagement.

These aren’t aspirational values on a wall. They’re constraints we impose on ourselves — and that you can hold us to.

01

Precision over platforms

The right tool for the right job — nothing more.

Most software companies sell platforms: generalized solutions designed to work adequately for thousands of firms, and that ask you to change how you work to fit the software. We build in the opposite direction — a narrow, precise module designed around the exact bottleneck you need to solve. The result feels invisible, because it fits.

02

AI as the engine, not the feature

Intelligence baked in from the first line of code.

A generation of software bolted AI onto existing workflows as an afterthought — a 'smart' button here, a summarization widget there. We build differently. Every module starts with the question: what would this workflow look like if intelligence were native to it? The answer is almost always simpler, faster, and more reliable than what came before.

03

You own it. Full stop.

No subscriptions. No vendor lock-in. No dependency.

When we finish, we hand you the keys. Full source code in your GitHub. Deployment docs written for your team. Architecture designed so any competent developer can maintain it without us. Software ownership is a business asset — and that asset should belong to you.

04

Craft over convenience

We take the harder path because it produces better outcomes.

The convenient path is to reach for the nearest off-the-shelf component and wrap it in a thin integration layer. We don't do that. Every module is designed from first principles for your context — your data, your systems, your team's technical literacy, your compliance posture. It takes longer. It produces software that actually works the way your firm works.

05

Small surface, deep integration

Narrow scope. Profound impact.

The instinct when solving a business problem with software is to build comprehensively — every edge case, every future requirement. We resist that. A module with a small, well-defined surface is easier to maintain and far less likely to break. We scope engagements tightly, build deeply within that scope, and hand off something your team can reason about completely.

06

The retainer is optional — and that's the point

We earn ongoing relationships. We don't engineer them.

We offer a post-handoff retainer. Some clients take it. Many don't. Both outcomes are fine. The retainer exists because software lives in a changing world — API contracts shift, rules change — and some firms want a partner to handle that. But it is never a condition of the engagement, and the software is never built in a way that makes it necessary.

How we operate

Six rules we hold ourselves to, in every engagement.

Not policies — commitments. If you ever feel one of these slipping, call it out and we’ll fix it or refund.

  1. 01

    We start every engagement by trying to talk you out of building software. If there's a simpler solution, we'll tell you.

  2. 02

    We never build more than you need. Scope creep is a failure of discipline, not a sign of thoroughness.

  3. 03

    We document everything as if we'll never speak to you again after handoff — because that might be true, and that's fine.

  4. 04

    We don't use AI to generate code we don't understand. Every line we ship, we can explain.

  5. 05

    We tell you when a problem is out of our scope. Referrals to the right specialist are part of the service.

  6. 06

    We price engagements by scope, not by the hour. You know what you're getting before we start.

The process

Four steps from “we have a bottleneck” to “we own the fix.”

Each step has a clear deliverable. You can stop after the discovery call or after the written scope — nothing is binding until you say so in writing.

Discovery call

30 focused minutes. You describe the bottleneck, we determine together if custom AI is actually the right tool — or if an off-the-shelf product would serve you better.

Scope & proposal

A precise written scope: what we'll build, how it integrates, what it will and won't do, and a fixed cost. No surprises after this document is signed.

Build & iterate

We build in the open. You see every iteration, you test it on your real work, and we tune until it earns its keep.

GitHub handoff

The full codebase lands in your repository. Architecture designed so any competent developer — including your existing one — can maintain it. You own it.

What handoff actually looks like

Not a login. A pull request.

On the last day of the engagement, we push to your repo, close the PR, and remove our access. This is roughly what the diff looks like, for an intake automation Sprint.

The retainer model

An ongoing relationship — if you want one.

Every engagement ends with a full handoff: source code in your GitHub, deployment docs written for your team, and an architecture any competent developer can maintain independently. That’s the baseline. You own everything.

For firms that want ongoing support, we offer a post-handoff retainer: modestly priced, monthly, no long-term lock-in. It covers updates, patches, minor features, and priority response.

StructureMonthly · no long-term lock-in
CoversUpdates, patches, minor features
Required?Never. Fully optional.

If you never call us again after handoff, that’s a successful engagement.

If this resonates, let’s talk.

Every engagement starts with a single 30-minute conversation. No pitch, no proposal until we understand your problem. If we can't help, I'll tell you.

Get in Touch