Grafá

Why Grafá

Proof, not a promise

Every app is run side by side with your own workbook on 120 random cases before you see it. You see how many matched; a difference that remains comes back to you as a question.

Today's behaviour first

Rebuilds go wrong when "how it works" and "how it should work" get mixed up. Grafá builds what your workbook does now; changes are your separate, recorded choice.

Ten questions, not ten meetings

The file answers most questions itself. You only get the ones it cannot answer, in plain language, with the impact of each.

Handover without the guesswork

When the workbook's author leaves, the knowledge usually leaves too. Grafá turns it into a document the next person can read and check, before the last day, not after.

You keep the knowledge

The summary and the full specification write down rules that today live in one person's head and a thousand cells. They are yours, whether or not you keep the app.

Tested before any customer

On public and made-up workbooks: the app had to match the workbook's results on 120 random cases.

WorkbookCases matching
Synthetic order book (prices, credit, commission, VAT)120 of 120after one general fix
Horizon Europe lump-sum budget template (European Commission)120 of 120first app
NREL JEDI land-based wind economic model120 of 120first app
US EPA WARM waste model, with large reference tables120 of 120first app
A trader's energy-position workbook from the public Enron archive; no brief, no answers120 of 120first app
JEDI wind model with its guide and notes removed; no brief, no answers101 of 120two precise questions left for the owner

Real owners' workbooks come next, in the pilot.

Compared with the alternatives

Rebuild by handLow-code toolsGrafá
Who works out the rulesa developer, from the workbook and interviewsyouGrafá, then you answer up to 10 questions
How you know it is righttesting by handtesting by hand120 cases against your workbook, every time
Time to a first versionweeks to monthsdays to weeks of your timehours