2 weeks.
To 2 days.
I shipped forms in the old system.
Saw what slowed every change.
Then built its replacement.
About two weeks → two days: elapsed development + testing for a product’s longest application form. Owner-reported.
120+ FORMS / 4 PRODUCTS / 1 ENGINEDocument Studio.
Make a document of your own.
Write it. Shape it. Take the PDF with you.
One product first.
Then all of them.
I proved the replacement on a new product.
It now supports the company’s forms across all four products.
The engineering
notes.
What changed under the hood?
Before: database configuration → Redis transformation → form-specific JSON logic → ReportLab → PDF in cloud storage. Three services, difficult tracing, and two API calls before I could see the result.
After: Redis supplies data. Explicit parameters guide business logic inside the Document Engine. Resolved values fill cloud-stored HTML/Jinja templates; WeasyPrint generates the PDF. One service, with visible HTML authoring.
How is a template approved?
Engineers check content and layout. Business approval is part of the Dev → QA → Demo → Prod journey.
What does “two weeks → two days” measure?
Approximate elapsed development and testing for a product’s main application form, the longest form. This is my reported outcome, not rendering speed or an average across all forms. Business-approval time is not specified.
From “why is this so hard?”
to a better way to work.
The studio is an independent browser demo. Create and export a real PDF; it does not connect to Afficiency’s production systems. Story animations use illustrative documents.
NEXT SESSION / FRIDAY ↗