Bespoke apps

A system built around how your business runs

When a job depends on a spreadsheet, an old tool and someone’s memory, Sysgraft builds the system it needs and connects it to your ERP. Specified with you first, then built, then kept running.

When a bespoke app is the right fix

Usually after Curavest work has found where a problem starts, and the cause turns out to be how information moves: retyped, copied into a workbook, or held in someone’s head.

  • The process is specific to your business and no off-the-shelf package fits without workarounds.
  • The data it needs is already in your ERP, and should go back there.
  • Several people need the same, current picture, not their own copy of it.

If a standard package would do the job, we will say so. A bespoke build earns its place only when the work is specific enough that a generic tool keeps getting in the way.

What has been built

The shape comes from the problem

Three examples, all live: a screen people work from all day, a job that runs overnight, and a quality platform.

A UK chemicals manufacturer, about £50m turnover

Production scheduler

Production was scheduled in a legacy Windows tool and an Excel workbook. A bespoke production scheduling application that replaced both, connected in both directions with the company’s ERP. Every field it writes to the ERP was agreed in the specification.

Live 14 days after the signed specification. Bought by the production scheduling team.

A UK wholesaler, about £7m turnover

Nightly enrichment

Every night it enriches the customer records in the ERP against Companies House data, scores spend potential, flags financial risk, and writes back only the agreed fields.

Live in 11 days. Bought by the managing director.

Quality management platform

Doctilla

Designed and built by Sysgraft, and used in Curavest’s quality work: corrective actions, nonconformities, supplier issues and audits in one place.

doctilla.co.uk

More on each build

Specification first

You see what will be built before it is built

Every build starts with paid discovery. Euan, who designs and builds every Sysgraft system, learns how the work runs, looks at the systems involved and tests how to connect to them.

The result is a specification you approve. It sets out:

  • what the app does, screen by screen or job by job;
  • which of your systems it reads from;
  • every field it may write back to, named one by one;
  • how you will test it before you accept it.

On a fixed-price build, discovery also produces a clickable prototype, so you can try the screens before you commit. The two ways to buy

Connected, not beside

Joined to your ERP, not another system to keep in step

A bespoke app that sits beside your ERP just adds a place to retype things. Sysgraft builds it onto the ERP: it reads what is already there and, where the specification says so, writes back to the fields agreed in it. Nothing else.

Your ERP stays the system of record. The people who work in it keep working in it.

Write-back. Most builds need no write access at all. Where one does, every field it can touch is named in the specification you approve.

Maintenance

Included, because your other systems keep changing

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

ERP vendors release updates and APIs change. A bespoke app that nobody watches stops working without warning and is found out by a wrong report. Sysgraft monitors every build and fixes what a change upstream breaks.

How a build runs, from discovery to maintained

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.