Skip to content
Scribbify

Our approach

Our software development process: evidence first, then software.

Our software development process treats every engagement as a question to answer with evidence: where does the work actually leak, what is worth building, and did it work? Software is how we answer it.

  • Scoped before it’s priced
  • Released as soon as it works
  • Judged on agreed numbers

01 Why we work this way

Big launches hide expensive mistakes.

Most software projects fail quietly. The scope is written before anyone watches the work being done, the launch arrives months later, and by then the assumptions inside it are expensive to change.

We run our own products, so we pay for our own wrong guesses. That is why every engagement starts with the people who do the work, puts one fix in your team’s hands early, and is judged by numbers agreed before anything is built.

For example, if your enquiries wait overnight, we start with the first reply to new leads, not a new CRM. If the CRM is the real problem, the first reply will show it within weeks.

02 How an engagement runs

Four steps, repeated.

The same loop for an internal tool, an AI agent or a funnel. Each pass fixes one leak and tells us what to do next.

  1. Step 01

    Understand the workflow

    We talk with you and the people doing the work, and follow how an enquiry or a job really moves today. We write down what we find, so you can check it.

    You get: A written picture of where the work stalls

  2. Step 02

    Choose the first gap

    Together we pick the one handoff or job that costs you most, and agree what should change, such as replies sent the same day or a report nobody has to build.

    You get: One agreed gap and what should change

  3. Step 03

    Implement the fix

    We build or connect what that gap needs, keep the tools that already work, and put it in your team’s hands as soon as it is usable.

    You get: A working fix your team uses

  4. Step 04

    Measure and improve

    We check the change in real use against what we agreed, adjust it, and only then decide with you whether the next gap is worth fixing.

    You get: A plain review, and a decision on what is next

03 Engagements

Three shapes of work.

Most clients start with a scoping sprint, decide on the evidence, and move to a build and then to running and improving it with us.

  1. Start here · 01

    Scoping sprint

    A short, fixed piece of work to find what is costing you most and decide what is worth building.

    • Conversations with you and your team
    • A written plan and design
    • A fixed scope for the first build
  2. 02

    Build

    The first fix designed, built and in use, then extended in small, agreed steps.

    • Something working from early on
    • Weekly progress you can try
    • Documentation and handover
  3. 03

    Run & improve

    We keep it running, watch the numbers with you and improve it as the business changes.

    • Monitoring, fixes and updates
    • New fixes as the business grows
    • A regular look at what the numbers say

How work moves through an engagement

  1. 01

    Scope

    Conversations with your team, a map of the leaks and a written plan for the first build.

  2. 02

    Fix the costliest job

    The job that costs you most, in use as soon as it works.

  3. 03

    Measure

    Checked in use against the measures agreed in scoping.

    If it doesn’t move the number, we change it before building more.

  4. 04

    Extend

    The next fix on the same system, or we keep running and improving it with you.

04 What you own

Everything we build is yours.

No lock-in by design. If you ever want another team to run it, they can.

  • The code

    In a repository you control, from the first commit.
  • The data

    In databases and accounts in your name, exportable at any time.
  • The accounts

    Hosting, AI providers and tools billed to and owned by you.
  • The knowledge

    Documentation good enough for another team to take over.
Where each part of a system lives: the code in a repository you control, the data in databases in your name, hosting and tools billed to you, and documentation another team could use.

05 Working together

A rhythm built for busy operators.

Engagements fit around a business that still has to run. This is what working with us looks like week to week.

  • One accountable lead

    One senior person owns your project from the first call. You always know who to ask, and they know your business.
  • A weekly working session

    Thirty minutes a week on what is done, what we learned and what comes next, shown in the real thing rather than slides.
  • Measures you can see

    The numbers we agreed at the start, such as replies, bookings or hours, are tracked in the open, so you judge progress by your business.
  • Security from day one

    Who can see and change what is set up from the start, everything is logged, and it runs in accounts you own.

06 Principles

What we hold ourselves to.

How we behave on every engagement, whatever we are building.

  • 01

    Keep the tools that work

    If a tool does its job, we connect it rather than replace it. Sometimes a spreadsheet or software you can buy is the right answer, and we will say so.
  • 02

    Build where it is justified

    Custom software has to earn its place: a process your tools cannot handle, or a cost that keeps coming back every week.
  • 03

    A person owns every decision

    Automation and AI carry the routine steps. Prices, exceptions and promises to clients stay with a named person on your team.
  • 04

    Measure the change

    Before we start, we agree what should change, such as same-day replies or hours spent on reporting, and we check it in real use.
  • 05

    Document it, and be clear who owns it

    We document what we build. Who owns the code, the data and the accounts is set out in the contract; our usual approach is that they sit in accounts in your name.

Questions

How an engagement runs, in four answers.

How does a project with Scribbify start?
With a short, fixed scoping sprint. We interview the people who do the work, map where time, leads and money leak, and finish with a written scope and system design for the first build.
Why fix one thing first?
Because a wrong assumption is cheapest to fix early. We put the fix for your costliest problem in use as soon as it works, check what it changed, and decide the next step on that. For example, a firm that loses enquiries before the first reply starts with lead response, not reporting.
How is progress reported?
One accountable lead runs the engagement, with a thirty-minute weekly working session on what shipped, what we learned and what comes next, using working software rather than status slides.
What do we own at the end?
Our published approach is that the code sits in a repository you control, the data in accounts in your name, and hosting and tools are billed to you, documented well enough for another team to take over. The contract fixes the exact terms.

07 Working theses

What we believe, until the evidence says otherwise.

Positions we hold from building for clients and running our own products. We revise them when the work proves us wrong.

  1. Thesis 01

    Fewer tools that agree beat more tools that don’t.

    Most businesses don’t need more software. They need the tools they already pay for to agree on the same client, deal and invoice.
  2. Thesis 02

    AI earns its place one checkable task at a time.

    Use it where the work repeats and a person can check the result. Widen what it may do only as it proves itself.
  3. Thesis 03

    Marketing is a system, not a campaign.

    Leads are lost between the ad, the inbox and the follow-up. Fix that, and every campaign lands on something that works.

08 Plain about fit

When we are not the right company.

We take on a small number of engagements at a time, so we would rather say no early than late.

  • You need a brochure website and nothing behind it.
  • You want the lowest hourly rate for a fixed list of features.
  • The problem is standard and software you can buy already solves it.
  • Nobody on your side can give the work an hour a week.

Start a project

Start with a scoping sprint.

Tell us the job or the part of your sales process that costs you most. A partner replies within one business day, and you decide on the evidence.

  • A partner reads every enquiry
  • A 45-minute working call
  • A written scope you can decide on

Or write to us at [email protected]

Our services

For example: enquiries wait overnight before anyone replies, delivery re-enters what sales already collected, or the weekly report takes hours to put together.

We use your details only to reply to this enquiry. No newsletters, no list sharing. See our privacy policy.