SignedDocsRepublic
Document signing for small teams, and a deploy process built for having no staging.
- Type
- Product
- Industry
- SaaS / business tools
- Platform
- Web application
- Role
- Design, build, deploy
- Status
- Live today: free AI business tools for freelancers (brief analyzer, proposal writer, contract checker, scope/quote/contract generators)
What made this hard.
A document signing and approval platform for SMB teams: upload a PDF, place signature fields, send it out, and track a multi-step approval chain, with an SPA for the signing app, a Laravel API and admin behind it, and static marketing pages in front.
Signing software has to be boringly reliable: precise field placement on a PDF, email flows that survive forwarding, an audit trail that stands up later, and a team model non-technical users can follow.
It also had no staging environment: a normal constraint for a young product and a dangerous one for a product whose failure mode is a document nobody can sign.
What we built.
- Locked the testing strategy in an ADR chosen specifically for the no-staging constraint: an isolated-database PHPUnit suite is the mandatory pre-deploy gate, and browser tests against production are a strictly read-only post-deploy canary: GET only, redirects asserted but never followed, so the canary can't pollute tracking. Green tests deploy canary automatic revert on red.
- Documented which surfaces the canary is blind to by design (admin-only pages) and gated those with unit tests, front-end tests and a one-off local browser run instead of pretending the coverage exists.
- Applied a “step zero” discipline before refactoring: triaged a red baseline and proved every failure was test drift against already-shipped behaviour, including a stale route comment contradicting the shipped middleware, before changing a line.
- Ran the pilot refactor on an admin-only controller, decomposed into Controller FormRequest Service Resource, precisely because its blast radius is small.
- Migrated the tools section from static pages to a database-backed section with category and tool models behind one shared shell, while each tool's interactive body stays a per-slug partial, an honest admission that an image editor and a VAT calculator share a shell but not a body. The migration also surfaced links to tools that never existed and tools that existed but were unlisted.
- Adopted a feature-flag convention with environment flags and reveal/hide commands, so a section can ship dark and be revealed atomically.
What it runs on.
Chosen to be maintainable for years, not to win an argument on the internet.
- PHP 8
- Laravel 12
- Vue.js
- Vite
- Tailwind CSS
- MySQL
- PHPUnit
- Playwright
- Nginx
Where it landed.
Deployment became a rehearsed sequence rather than an act of nerve: tests, backup, config cache, FPM reload, canary sweep of the key routes, documented rollback.
The same codebase later hosted Parley, the AI conversation coach inside this product, which is only sane to attempt on a product whose deploy path you already trust.
Need something in this territory? This is Custom web app development work. Start from all services or see pricing.
Related case studies.
Your project
Tell us what you're building. We reply within two business days.