Developer Backlog
9 Epics · Feature checklists · User stories · Acceptance criteria
CRM Foundation
Feature Checklist
User Stories
As a salesperson, I want to create a customer and project before starting a quote, so that all quote data is tied to a real account.
As a estimator, I want to find previous customer projects quickly, so that I can reuse context and avoid re-entering information.
Acceptance Criteria
- User can create/edit/archive customers and projects
- Projects belong to customers
- Notes and attachments saved per project
Quoting Engine
Feature Checklist
User Stories
As a estimator, I want to create a standard tooling quote using formulas, so that repeat work is priced quickly.
As a estimator, I want to a separate path for fiberglass parts, so that I can use flexible logic when the standard multiplier does not fit.
Acceptance Criteria
- User can create a draft quote and choose a quote mode
- Square footage stored on quote
- Standard formulas compute price
- User can override with manual adjustments
- Expected material usage generated
Quote Output & Approval
Feature Checklist
User Stories
As a salesperson, I want to generate a PDF from a quote, so that it can be sent to the customer in a clean format.
As a operations user, I want to a quote to remain inactive until approved, so that only sold work becomes a real job.
Acceptance Criteria
- User can export quote PDF
- Quote status defaults to draft
- Approved quote converts to job
- Duplicate conversion blocked
Job Creation & Traveler
Feature Checklist
User Stories
As a operations manager, I want to approved quotes to become jobs automatically, so that the shop does not re-enter information.
As a shop-floor lead, I want to a traveler/spec sheet generated from the quote, so that the production team sees the correct instructions.
Acceptance Criteria
- Job created from approved quote
- Traveler/spec sheet exists for each job
- Key quote fields flow into job
- Traveler can be edited without losing quote history
Department Workflow Engine
Feature Checklist
User Stories
As a operations user, I want to a job to move from department to department, so that the shop always knows where work is.
As a department lead, I want to to see which steps are pending, active, or blocked, so that I can manage throughput.
Acceptance Criteria
- Departments and steps can be configured
- Each job has step instances
- Users can update step statuses
- Notes can be added at step level