How a build runs

From the problem to software you rely on

What happens at each stage, what you do, and where you can stop. The specification is in your hands before anything is built.

The stages

  1. Before Sysgraft

    The starting point

    What happens

    Most builds start from a Curavest finding: the cause of a repeat problem has been traced, and the fix depends on software. A direct enquiry starts the same way, with the problem rather than the software.

    What you do

    Bring the problem. For a direct enquiry, the systems check or a conversation is enough to start.

  2. Stage 1

    Paid discovery

    What happens

    Euan learns how the work runs, looks at the systems involved and tests how to connect to them. On a fixed-price build, discovery also produces a clickable prototype.

    What you do

    Give access to the systems in scope and time with the people who do the work. Answer questions as they come up.

  3. Stage 2

    Specification and sign-off

    What happens

    A written specification: what will be built, which systems it reads, every field it may write back to, and how you will test it.

    What you do

    Read it, ask questions and approve it. Or stop here. Ordering discovery does not commit you to a build.

  4. Stage 3

    The build

    What happens

    Built onto your existing systems, with a progress report every week. Platform builds have gone live 8 to 14 days after the specification was signed.

    What you do

    Make decisions when asked, then test the software against the criteria in the specification.

  5. Stage 4

    Go-live and the first 90 days

    What happens

    On a fixed-price build, a 90-day warranty. On a subscription, 90 days of tuning: adjustments made against the live system as your team uses it.

    What you do

    Use it, and tell us what needs adjusting.

  6. Ongoing

    Maintained

    What happens

    Maintenance is included with every build: monitoring, fixes when your connected systems change, and improvement. It is not sold on its own.

    What you do

    Report anything that looks wrong. Commission changes when you want them.

Where you commit

One decision point, after you have read the specification

Everything before sign-off is there to show you exactly what you would get. Everything after it is the build you approved. Every figure is agreed in writing before you pay it.

Under the subscription, nothing beyond discovery is owed until the software is live.

Write-back. The specification names every field the software may write to in your systems. Nothing writes anywhere else.

The two ways to buy

Questions about a build

What if the specification is not right?
Then you do not go ahead. Discovery is paid for on its own, and approving the specification is a separate decision. Ordering discovery does not commit you to a build.
How often will we hear how the build is going?
Every week during the build, in writing.
Do we have to replace our ERP or CRM?
No. Sysgraft builds onto the systems you already run. Your team keeps working in them.
What do changes cost after go-live?
On a fixed-price build, changes are charged at the day rate in your quote when you commission them. On a subscription, changes are included for the first 90 days, then charged the same way. Every figure is agreed in writing before you pay it.
Who does the work?
Euan Pallister designs and builds every Sysgraft system, with the Curavest team behind the work.

Start with the free two-hour workshop

Most Sysgraft work begins with Curavest’s Operational Improvement Workshop: two hours on one problem that keeps coming back, on site or on Teams. No obligation, and no records needed. If the answer turns out to need software, that is a separate decision, for later.