Its founders spent the first decade of their careers as consultants and architects inside large, high-stakes enterprise and public-sector programs — banking back-offices, government information systems, regulated finance, document-heavy operations. Project after project, they watched the same failure pattern repeat, and it had nothing to do with how clever the technology was.
Requirements were planned on paper, by imagining the software. Business people were asked to specify, in detail and in advance, how software functions should behave — then those functions were designed on paper, signed off, and only much later built. But a business manager's job is to run the business well, not to design software. Asking them to picture a system they'd never seen produced confident specifications that turned out to be wrong the moment a working screen appeared.
Change broke everything. Real organisations don't hold still. Regulations shift, processes evolve, priorities move. In a paper-first, big-design-up-front world, every change re-opened the whole chain — re-specify, re-design, re-develop, re-test — and the budget and timeline paid for it. And feedback came too late: by the time end users and business managers could actually touch the system, the expensive decisions had already been made.
The founders concluded that the problem wasn't the people or the effort — it was the method. You cannot reliably design a complex system on paper with people whose expertise is the business, not the software. You have to let them react to something real, early and often.
So they imagined a different way of building: plan against actual functional skeletons, not paper abstractions. Stand up a working backbone fast, put real, clickable prototypes in front of end users and business managers in the first weeks, gather direct feedback, and let the system converge on what the organisation actually needs — while a stable, engineered backbone keeps the whole thing dependable under change.
That idea needed a foundation that didn't yet exist in a form they trusted, so they built one: a low-code framework (WSF — originally the Workflow Solution Framework) that could stand a real, working system up quickly, absorb change cheaply, and still carry the weight of a regulated, mission-critical deployment. They proved it across repeated client engagements — and then, in 2011, founded Appsint to develop the framework as genuine IP and to deliver complete, "heavyweight" enterprise solutions with it, wall-to-wall: from the first idea to years of operation.
That is still exactly what Appsint does.