Approach

How the work gets done

What we believe about this work, how a project runs from the first call to handover, and the three ways to work with us.

Principles

What we believe about this work

Six commitments that shape every scope we write.

  • 01

    Start with the business problem

    We begin with what is slowing the business down and what a good outcome looks like. The tools get chosen after that.

  • 02

    Get the data right first

    Reports and AI are only as good as the numbers you feed them. Before we build anything on top, we make those numbers trustworthy. Often that means finding out why two systems disagree about the same customer.

  • 03

    Technology inside the tools you already use

    We build into the systems your team works in every day. Something that lives in a separate tab does not get opened.

  • 04

    Automation that still asks a person before the big decisions

    The routine runs on its own, and the decisions that carry risk stop for a human sign-off with a record of who approved what.

  • 05

    You own everything we build

    What we build, the documentation, and the training to run it are yours. When the project ends, nothing depends on us to keep running.

  • 06

    Everything in writing

    Scope, price, and timeline are agreed before work starts. When something changes mid-project, the document changes first and you approve the revision.

Our approach

Four phases

  1. Discover

    A thirty-minute conversation about the business problem, what a good outcome looks like, and whether we are the right partner.

  2. Define

    A written scope listing what you get, when each piece lands, and the finish date, approved by you before anything starts.

  3. Deliver

    Working results at every milestone, reviewed with the people who will use them. Course corrections happen early, while they are still cheap.

  4. Hand over

    Documentation and training until your team runs it without calling us.

Ways to work together

Three ways to work with us

Start with an assessment, bring us a full project, or keep us on call.

  • Assessment

    A short project to understand the problem and work out what fixing it is worth. You get a written plan that says what to fix first, what it should cost, and what it returns.

    Duration2 to 3 weeks
    PricingFixed fee
    You getA written plan with costs and priorities
  • Project

    The whole job delivered in stages you can see, from design through to handover, with your team trained to run it.

    Duration3 to 12 months
    PricingFixed fee, billed by milestone
    You getA working system your team owns
  • Advisory

    An ongoing arrangement for businesses that want a technology partner on call. We review your plans, weigh in on vendor choices, and pick up the phone when something breaks.

    DurationOngoing, monthly
    PricingFixed monthly fee
    You getA partner who knows your business
Questions

What people ask on a first call

How fast does this move?

An assessment takes two to three weeks. A full project runs anywhere from three months to a year depending on how much of the business it touches, and you see working results at the first milestone, so you know early whether we are the right partner.

What does it cost?

Assessments and projects are a fixed fee against a written scope. The scope names what you get, when each piece lands, and the price, and you approve it before work starts. Advisory is a fixed monthly fee.

We have no technology team. Does that matter?

No. We build for the team you have, write the documentation in their language, and train them until the system runs without us on the phone.

Who owns what you build?

You do. What we build and the documentation are yours, and the accounts behind it are set up in your name.

What happens to the systems we already use?

We build into them. Replacing software nobody complained about is a project risk of its own, so we save that advice for the rare case that earns it.

Is our data safe once AI is involved?

Your data stays in your own accounts, under your own controls. The written scope names which tools touch what and on what terms, and you approve it before anything is connected.

Thirty minutes settles most of it.

Bring the problem. We come back with our take on the fix, and if the fit is real a written proposal follows.