Specification-driven, not vibe-driven
AI makes software development faster, provided it stands on the right foundation. That is why at Wercstat we don’t start with code, but with specifications. We map your needs in detail and capture them in structured documents: entities, processes, screens, rules and constraints. Only once that foundation is sound do we start building.
This clearly sets our approach apart from vibe coding; improvising with a chat prompt and hoping working software rolls out. For business software, and certainly for ERP, that is not an option. The specification is the source of truth; AI is the tool that helps us turn that truth into working software faster.
Step 1: Capture needs in specification documents
Together with you, we map your business processes and translate them into clear specification documents. Not loose notes, but a coherent whole that is readable for us and for you.
Domain model: which entities play a role, and how do they relate?
Processes and workflows: which steps, which decisions, which exceptions?
Screens and interactions: who sees what, who does what, and when?
Rules and constraints: what must always hold, what must never happen?
These documents are not throwaway. They run alongside the entire project as a living reference, through changes, extensions and delivery.
Step 2: AI and framework skills speed up the build
With the specification as the starting point, we bring in our AI skills and the Wercstat framework. The skills read the model, recognise patterns that recur in every ERP project, and generate in seconds what would otherwise take days of manual work: screens, forms, overviews, integrations, workflow steps.
Because the framework is model-driven and type-safe, that speed does not produce clutter. What is generated is consistent with the rest of the system, errors are caught at compile time, and every generated component can be refined by hand where the domain calls for it.
Step 3: Controlled, not let loose
For us, AI is supporting, not steering. Every step goes through a structured review:
Code review by experienced developers: no line reaches production unseen.
Automated tests: all business functionality is verified with automated tests that run on every change.
Checking against the specification: what is built must demonstrably cover what was agreed.
This way we combine the speed of AI-driven development with the solidity that business software simply needs. No surprises afterwards, no black-box code that nobody dares to touch anymore.
Step 4: Implementation and ongoing development
Delivery follows the specification and the tests that go with it. What we agreed is what you get, and it demonstrably works. Implementation happens in short iterations with direct feedback, so disruption to your operations is kept to a minimum.
And because the specification documents grow with your business, ongoing development stays just as structured as the first delivery. New modules, changes to existing functionality, integrations with new systems, always via the same route: specify, generate, review, deliver.
Step 5: Operational management
An application is not finished at delivery. As soon as it runs in production, operational management begins. Wercstat continues to play an active role there, as light or as intensive as you wish.
Central error logging: all warnings and error messages the application generates are automatically collected in the cloud and remain visible there. Nothing is lost between separate log files on separate servers.
Priority-driven alerts: depending on severity, alerts are emailed to your own support department, to Wercstat support, or to both. Critical errors land directly in the right place, without anyone having to comb through logs by hand.
Operational statistics: the application continuously produces figures on how it is used: which screens, which processes, which lead times, which peak moments. These statistics are available to your own IT department and to Wercstat as cloud administrator.
Shared management: you decide who handles what. If you have your own IT department, Wercstat acts as second-line support for matters that touch the framework or the generative layer. If you don’t have that capacity in house, Wercstat takes on the full operational management.
This way the application does not become a black box after delivery, but a system that is actively monitored, adjusted and developed further based on what happens in practice.
Ready to get acquainted? Get in touch for a no-obligation conversation.