Sysgraft is one person.
That's the fact a cautious board notices first, so it goes first. Euan Pallister runs the discovery, writes the specification, builds the system, and maintains it.
The conversation is with Euan himself. No salesperson, no obligation. Thirty minutes, online or by phone.
Operations first. Engineering second. In that order for a reason.
Before writing software, Euan spent his career on the other side of it: operations, manufacturing, account management and physical product development — including five years running his own business in third-party product innovation. Then more than ten years of software engineering, specialising in ERP API integration, hands-on across manufacturing, distribution, wholesale and logistics.
The order matters: discovery works because the person asking the questions has sat where you sit, and the specification is written by someone who knows what the answers mean.
Why the firm works this way.
Most of what's unusual about Sysgraft is a decision about how software should be sold to a business like yours — decisions a firm of one can make and keep:
- No salesperson. Nothing can be promised that the builder can't deliver, because the person who says it is the person who ships it.
- Specification before commitment. What you approve is what gets built — the promise is a document, not a pitch.
- One platform, adapted per client. It's what makes a 10–14 day build and no development invoice possible: the foundations already exist, and you pay for the adaptation through the subscription.
- The AI reads; it never writes. Bespoke modules write only to the specific, named fields in the specification you approve.
- The exit is published. Formula, year-bands and a worked example, before you sign — clause 18.1 of the Master Terms.
None of that is a slogan. Each one is checkable — in the order of events, in a document you hold, or in a published term.
What happens if something happens to him.
A one-person firm is a concentration risk. A board is right to weigh it, and this page won't talk it away — the answer is contractual, not reassuring.
The code sits in escrow.
If Sysgraft ever defaulted, it passes to its clients.
Maintenance isn't ad hoc.
Health monitoring and maintenance run remotely for the whole subscription, inside the fixed fee.
Your data is never trapped.
At any ending — chosen or otherwise — it comes back to you in full.
Seven commitments, written from your side of the table.
- 1 — You approve exactly what will be built before you owe a subscription. The specification comes first; the commitment follows it.
- 2 — Your exit cost is published before you sign. The formula, the year-bands and a worked example are in clause 18.1 of the Master Terms.
- 3 — Your data is never mined, resold, or trained on. Sysgraft only uses it to answer your questions — nothing else.
- 4 — If you leave, your data comes back in full — and the software stops. Both halves, stated together, because a promise that hides its second half isn't one.
- 5 — The service doesn't quietly degrade after you've signed. Health monitoring and maintenance run for the whole subscription, inside the fixed fee — that's the commitment in concrete form.
- 6 — No outsourced work is ever passed off as Sysgraft's. The person you deal with is the person who does the work.
- 7 — If Sysgraft fails, the code passes to its clients. In escrow, in writing.
The conversation is with him.
If you've read this far, you know who you'd be talking to. The conversation is about your business, not about him — the decisions that are hardest to make well, what you can't currently see, and whether Sysgraft is actually the right answer. If it isn't, you'll leave knowing more clearly what is.
No salesperson exists to hand you to. No obligation. Thirty minutes, online or by phone.
Check whether your systems fit →
A short form about the systems you run. Tell us where to send it and you'll get a straight answer on compatibility, plus practical guidance on managing rising AI use in the business — useful whether or not we ever speak.