A form builder that took IT out of the loop

Large organisations accumulate forms faster than any engineering team can service them. Onboarding checklists, compliance declarations, internal requests — each one arrives as a ticket, waits in a queue, and is built by someone who is not the person who understands what it needs to ask.

The bottleneck is not technical difficulty; it is that every trivial change requires an engineer. The teams who own the process cannot change their own forms, and the teams who can change them do not own the process.

The usual escape route makes things worse. Departments reach for whatever consumer form tool they can sign up for themselves, and within a year the firm has submissions scattered across a dozen external accounts, outside its own access controls and retention rules. In a regulated professional services setting that is a governance problem, not an inconvenience.

So the requirement is genuinely two-sided: give the people who own a process the ability to change it, without giving up the control that made the queue exist in the first place.

We built a form creation platform for internal use at the firm, designed so administrators could construct and manage forms themselves through a drag-and-drop interface rather than a specification handed to developers.

Different groups within a firm that size need different reach, so access is role-based: who can create, who can edit, who can see submissions. Governance stays intact while the work moves to the people closest to it.

Submissions feed a built-in analytics dashboard, so the data is read where it lands rather than exported and reconciled elsewhere. Every export step is a copy that can drift, and a copy in a spreadsheet is outside the access model the platform exists to enforce.

We delivered the whole stack — form logic, backend, frontend and UX. The logic layer is the part that decides whether a builder like this survives contact with real processes: conditional questions, validation and the rules that make a form behave differently depending on what has already been answered.

Administrators build and change forms without engineering involvement, and read the results in the same place they created them.

Complex internal workflows run through a single governed platform instead of a queue of one-off builds, which removes the incentive that sends departments to external tools in the first place.

Engineering time stops being consumed by form requests. That capacity does not disappear — it moves to work that actually needs engineers, which is the real return on a platform like this.