Client workflow
Focus Graphics Platform
A client platform I own from product framing through implementation, covering quotes, proof collaboration, invoicing, payments, and production handoff.
- Year
- 2024–present
- Role
- Product owner & solo engineer
- Status
- Live
At a glance
- End to endworkflowA complex B2B workflow from intake through production lives in one system.
- Liveproof reviewCustomers and staff can review proofs together in the portal.
- Self-hostedhosting modelThe stack runs on infrastructure I operate directly.
Inside the admin
Real admin screens captured with synthetic demo data so the workflow is visible without exposing customer information.
Problem
Quoting, customer proofs, invoicing, payments, and production were connected by manual handoffs. I built one platform around that workflow, including the revisions, custom line items, and production exceptions the team handles every day.
Result
The live system now carries the workflow from lead intake through production while keeping staff and customer review in the loop.
- One system
for a complex B2B workflow
Quotes, proofs, invoices, payments, and jobs no longer live in disconnected tools.
- Before press
artwork changes are visible
Pixel comparison and a concise summary help catch changes before they become expensive production mistakes.
- Portal-first
customers can act directly
Customers can review proofs, accept quotes, and pay invoices without waiting on back-and-forth coordination.
- Owned stack
the operating model stays flexible
I can adapt the workflow as the business changes because I run the code and infrastructure.
Role
I handled the product and technical work directly:
- Workflow framingMapped how the shop moves from lead to quote to proof to payment to job completion.
- Architecture and implementationBuilt the customer portal, admin surfaces, data model, API routes, and deployment model myself.
- Operational fitDesigned for revisions, custom line items, proof approval, and production coordination.
- Live operationsOperate the production system, database migrations, error tracking, and ongoing changes as the workflow evolves.
Constraints & Decisions
A few decisions shaped the platform:
- One shared data modelQuotes, proofs, invoices, and jobs stay connected as work moves through the shop.
- Proof collaboration before productionReal-time comments and live cursors were worth the complexity because unclear approvals create costly rework once production starts.
- Compare against known evidencePixel diff and file parsing establish what changed before a short summary helps staff review the result.
- Self-host for controlI manage the infrastructure, deployment process, and operating costs directly.
Lessons
- Fit the workflow closelyRevisions, custom line items, and production handoffs need first-class support because they happen every day.
- Base summaries on concrete changesPixel diff and file parsing establish what changed before the system summarizes it for review.
- Real-time collaboration belongs where delays are expensiveLive cursors and comments help resolve unclear approvals before production begins.
- Self-hosting requires ongoing careOwning the infrastructure adds maintenance work and makes it easier to adapt the system as the business changes.
More work
Let's talk.
Need to replace a manual business workflow? I can help turn the handoffs, spreadsheets, and disconnected tools into a focused system shaped around your team.