PrintVoize

Problem

• Quotations, invoices and job records lived across spreadsheets, chat threads and printed paper.
• Every quote was rebuilt manually, so pricing drifted between jobs and revisions were hard to trace.
• No single place answered simple operational questions: what was quoted, what was approved, what was billed.
• Administrative work scaled linearly with order volume, which capped how much the business could take on.

Approach

1. 01Discovery

   Mapped the real quotation-to-invoice path with the people doing the work, including the informal steps that never appeared in any documented process.

2. 02Architecture

   Modelled clients, quotations, jobs and invoices as one relational domain so a document could move through states instead of being retyped.

3. 03UX

   Designed dense, keyboard-friendly screens for daily operators rather than a marketing-grade dashboard nobody would use twice.

4. 04Engineering

   Built a typed full-stack application with server-side data access, role-aware permissions and printable document generation.

5. 05Integration

   Connected authentication, storage and document output so records stay consistent from first quote to final invoice.

System

1. Frontend — Next.js (App Router)L1
2. API / Server ActionsL2
3. Prisma ORML3
4. PostgreSQL / SupabaseL4
5. Auth + File storageL5

Outcome

• Quotation, invoicing and job tracking consolidated into a single platform.
• Documents are generated from stored records instead of being recreated per job.
• Operational history is queryable, so status questions are answered from the system rather than from memory.

Tech stack