Document creation has a blank page problem. But the blank page isn't the real problem, it's a symptom of not knowing what to write, in what structure, with what language, for what purpose.
SmartDocs started from a simple observation: the tools that store business documents and the intelligence needed to write them have never been in the same place. You find the NDA template. You open it. You stare at "[PARTY A]" and "[DESCRIBE SCOPE OF WORK]" and realise that the template hasn't actually helped you write anything, it's just given you a more structured version of a blank page.
Auditing how teams actually worked made the failure modes visible.
The Boilerplate Bottleneck: Teams kept their own local copies of templates because the shared drive was disorganised and nobody was sure which version was current. Three people on the same team using three different NDAs was not unusual.
Blank Page Paralysis: Providing the right template in the right version still didn't solve the drafting problem. Sections like "Market Analysis" or "Long-Term Vision" stopped people cold. They knew what they meant, but not how to express it in the register the document required.
The Filing Cabinet Trap: Existing document software was built entirely around storage and retrieval, not creation. It answered the question "where is my document?" It offered nothing for "how do I write this document?"
Two users with opposite needs, one interface to serve both
The founder needs to move fast. They're creating a pitch deck, an investor memo, a partnership NDA, often for the first time, under pressure, without a legal or comms team to lean on. They need guidance more than storage. They need the platform to understand the context of what they're making and help them say it correctly.
The operations manager needs control. They're responsible for document governance across a team or department. They need version certainty, hierarchical organisation, status visibility, and the ability to audit what's been sent to whom. They don't need help writing, they need help managing.
Those two users are often in the same organisation. The platform had to serve both without the founder feeling buried in admin and without the ops manager feeling like they'd lost control of their document library.
The AI Wizard: designing conversation as interface
The core innovation in SmartDocs is the AI-Guided Generation Wizard, a modal-based creation flow that asks one focused question per screen rather than presenting a full form. The wizard doesn't ask "describe your business", it asks "what is your company's primary product or service?" It doesn't ask "describe the scope", it asks "what deliverables will you provide under this agreement?"
The difference is constraint. A blank text area with a broad instruction produces anxiety. A focused question with a specific scope produces an answer. The wizard turns the entire intimidating task of writing a complex business document into a sequence of answerable questions that most people can get through in under five minutes.
Getting the questions right was the hardest part of the project. Too broad and they weren't helpful. Too narrow and they didn't accommodate variation between industries or document types. We iterated through multiple question sets for each document type, NDA, Pitch Deck, Proposal, SOW, testing the outputs the AI generated against the quality a human professional would produce.
The progress indicator: one of the smallest decisions with the biggest effect on completion
The original wizard design had no progress indicator. You answered a question and the next one appeared. Testing showed high anxiety, users didn't know how far through the process they were, which made every question feel potentially endless.
Adding a segmented progress bar, five segments, one filled per completed question, changed completion behaviour dramatically. Users who could see they were on step 3 of 5 continued. Users who couldn't see progress abandoned at roughly the same point, consistently. The bar gave them a contract: this will end at a predictable point.
The bar also changed the pacing of how users answered questions. Knowing there were only two more questions made them more deliberate with each one rather than rushing to get through an uncertain process.
The sidebar: building a document library that doesn't feel like a filing cabinet
The persistent sidebar serves the ops manager use case. Clean table view, document name, type badge, status pill, last modified date. No folder hierarchy to maintain. Status pills (Draft, In Review, Finalised, Sent) do the work that folders usually do, but without requiring the user to decide where something lives.
File-type badges were important for the ops manager specifically. Being able to see at a glance that a row is a DOCX rather than a PDF, and therefore still editable, removes a decision point that would otherwise require opening the file. Small legibility improvements compound significantly across a library of hundreds of documents.
Open-ended AI prompts are the wrong tool for this job
One alternative model we explored was a chat interface, describe what you want, the AI produces it. We built it. We tested it. It failed in the same way every time: users who didn't already know how to write the document also didn't know how to prompt for it. The chat box was just a more technology-forward blank page.
Constraining the AI into a structured wizard, where it asks questions rather than waiting to be prompted, changed the dynamic entirely. The AI becomes a guide rather than a tool. The user's job shrinks from "write a document" to "answer these questions." Those are very different cognitive tasks, and only one of them produces consistent output quality.
That insight carries beyond SmartDocs. Generative AI is most useful to non-experts when the interface does the prompting for them.