Websites, automation, software and AI, built around how you actually run.

We build the systems and teach the people who use them. Your tools stay, your data stays yours, and a person on your team approves anything that goes out.

What we build

From the first inquiry to the final invoice.

Eighteen services in five groups. Pick the one that hurts most, or start with the audit and let it tell you where to begin.

02

Take the copying and chasing out of the week

The retyping, reminding and report-building done the same way every time, with a person handling the exceptions.

05

Start right and make it stick

Find out where AI is worth it, get your data into a shape it can use, and teach your team to run what we build.

See it working

Every clip ends at a finish line.

Fictional companies. Every clip is a real screen recording of the same staged product, not a mockup.

Cedar & Stone, renovation

A request buried in a client email becomes change order #4 for $3,850, drafted for approval before any work starts.

Keystone, property management

Six issues overnight. One deferred dispatch. $1,240 not spent at 1.8× rates.

Hartley & Voss, law firm

6.5 unbilled hours found and drafted. $1,950 recovered this week.

Fleetline, delivery

One failed stop. Seventeen promises re-made for $23.

1 / 4

How we work

Think first, then build.

We learn how you run before we build anything. Discovery is a fixed fee agreed before we start, and you keep what it produces whether or not we build.

  1. 01

    Discovery

    Fixed fee · 2 to 3 weeks

    We learn how the business actually runs: who does what, in which tools, and where the time and money leak. Nothing gets built and nothing in your systems changes.

  2. 02

    Build

    Scoped in hours, quoted in writing

    One workflow or system at a time, starting with the one that costs you most. Each build is scoped and quoted in writing before any work begins, and built in your accounts.

  3. 03

    Run and improve

    As needed

    Once it’s live, we keep it healthy and keep it honest: monitoring, model and cost management, and new builds when your work changes.

What we hold to

  • We learn how you run before we build

    Discovery comes first: conversations with your team, a walk through your tools, a baseline of where the time goes and a ranked list of opportunities. You keep the outputs whether or not we build.

  • You own everything

    Code, data, accounts and documentation live in your accounts from day one. Another developer could pick it up from the handover pack.

  • Read-only by default

    We connect to your systems to read. Anything that writes, sends or changes data is a separate, narrow permission you approve.

  • A person approves what goes out

    AI drafts. Someone on your team approves before a client, a supplier or the books see it, and every approval is recorded.

  • Built to be checked

    Totals reconcile against the source. Every AI draft records what it read. History is dated, so you can see what changed and when.

  • Measured against a baseline

    We measure the before, so the after means something.

  • We teach it

    Training for the people who use it, written guides, and a named owner on your side. ThinkFirst runs a live AI-education platform, so teaching is our home ground.

What AI never does alone

These always go to a person on your team first.

  • Move money, or promise it
  • Send the first message to anyone in your name
  • Set a price or a quote
  • Make a legal commitment
  • Answer a complaint
  • Delete records or make bulk changes
  • Make an exception to your own rules

Questions

Questions worth asking first.

No. We connect to the tools you already run and build only the pieces that are missing. If one of your tools is the actual problem, we’ll say so and explain why, and the decision is yours.

You do. Code, data, accounts and documentation live in your accounts from day one. That includes the domain, hosting, database, AI provider keys and phone numbers. Another developer could pick it up from the handover pack.

Discovery is a fixed fee agreed before we start. Builds are scoped in hours and quoted in writing before any work begins.

We connect read-only by default, and anything that writes or sends is a separate permission you approve. Everything runs in your accounts, with access by role. We choose the AI provider per task, usually Anthropic (Claude) or OpenAI, under an account in your name and on business terms that don’t use your data to train their models by default. We’ll show you those terms before we start. Your own privacy obligations stay with your business, and we build to your policy.

Discovery takes 2 to 3 weeks. Each build after that is scoped in writing, one workflow or system at a time, so you know what you’re getting before any work begins.

You keep everything. The discovery outputs are yours whether or not we build. Anything we build is already in your accounts and your repository, with a handover pack written so your own team or another developer can carry on without us.

Yes. Construction has the deepest page here, but the method is the same anywhere work comes in, gets done and gets billed: property, professional services, clinics, retail, agencies, education, logistics and the trades.

Yes, and we’d like to. They grant our access, see the repository, approve each permission and get the same handover pack you do. If you have a security or privacy process, we work inside it.

Tell us what you run. We will tell you honestly if we can help.

Five short steps. We read every brief ourselves.

Start a project