Paste a single operating procedure. Each step is matched line-by-line against a corpus of the requirements corpus and read as standard (out-of-the-box), config (clean-core extension), or custom(genuine build) — so you know what's bespoke before you commit a budget. No sign-up funnel, nothing saved.
About the single-SOP read
One standard operating procedure is the smallest useful unit of scope. Paste it and Specforge decomposes the procedure into the requirements it actually implies, then reads each one against a corpus of proven implementations, architect-reviewed as it grows: standard out of the box, achievable through configuration, or genuinely custom. It is the fastest way to see how much of the way you work today survives contact with a new platform.
How it works
1Paste one procedureAny SOP — the steps as written in your own process documentation. No structure or rewriting required.
2See the requirements it impliesThe procedure is decomposed into discrete requirements, because a single SOP step usually carries several.
3Read the verdictsEach requirement is classified standard, config, or custom, so you can see which parts of the procedure the platform handles natively and which parts need building.
What you get
A standard-versus-custom read on a real procedure of yours, in minutes
The requirements hidden inside a procedure that reads like a single step
An early signal of where a process re-design would be cheaper than a custom build
Who it's for
Process owners and functional leads who want a concrete answer about their own way of working, and programme leads sampling a handful of procedures before committing to a full scope exercise.
Common questions
Why start with one SOP instead of the whole set?
Because a single procedure is enough to see the pattern, and it takes a minute. Once the read looks useful, the guided builder turns a full set of SOPs into RFP requirements.
What if my SOP is written for the old system?
That is the useful case. Procedures written around legacy screens and workarounds are exactly where the standard-versus-custom split gets interesting — a step that exists only to work around an old limitation often disappears entirely.
Does a custom verdict mean it cannot be done?
No. It means the capability is not delivered out of the box and would need development, which carries cost and upgrade risk. Sometimes the right answer is to build it; sometimes it is to adopt the standard process instead. The read gives you the choice explicitly.