Clients
Verify client record exists
Contact and job history in one place
Review recordBlueprint journey
Lesson 2 / 36
0 completed
Next best lesson: Start Here: How to use Blueprint week by week
Guided operating lesson
BuilderBuddi execution map
Know exactly where every workflow lives so you stop losing time hunting for the right place in the app.
Start Here9 minFoundational
Who this is for
Contractors who opened BuilderBuddi, clicked around, and felt uncertain about how everything connects.
Why it matters
Without a clear mental map, contractors default to using the easiest visible feature rather than the right one — which creates disconnected records and missed follow-up.
Lesson outcome
You have a clear picture of the five-step work loop and where every supporting tool fits so you can navigate the app with confidence.
Real-world problem
The app feels like a toolbox with no labels.
Every feature in BuilderBuddi supports a specific part of the contractor workflow — but without a map it just looks like a list of menus. Contractors end up creating quotes without linking them to jobs, taking notes without linking them to context, and invoicing without a clear job record behind it.
A painter creates three separate quotes in the Quotes section without ever creating a job, then cannot find the relevant notes when the client calls with questions a month later.
Why this happens
No orientation before starting to use it
Most contractors open a new tool and start clicking on the most obvious menu items. Without understanding the intended workflow, they build habits around the path of least resistance.
Each feature looks independent
Jobs, quotes, invoices, notebooks, and documents all have their own navigation. Without seeing them as a connected flow, they get used as separate tools rather than stages in one operating loop.
Professional standard
Jobs are the operating center — everything connects to them
The correct workflow is Client → Job → Quote → Invoice → Payment. Every note, document, and task should be linked to the job it belongs to, keeping records clean and readable.
Upstream tools feed jobs — they are not standalone
The notebook captures site reality fast. Calculators inform quote decisions. Documents are the audit trail. All three exist to support job execution, not to operate independently.
Step-by-step operating system
Learn the five-step work loop
1
Client record first
Every piece of work starts with a client record. This keeps contact history, job history, and communication in one searchable place.
BuilderBuddi: Open Clients and create or verify the client record before creating the job.
2
Job as the operating hub
Create a job for every piece of work. The job is where scope, tasks, notes, quotes, invoices, and timeline all connect.
BuilderBuddi: Create a job from the client record. Set the status, add a title, and write a one-sentence scope description.
3
Quote from the job
Create quotes from inside the job, not from the Quotes menu directly. This keeps quote and job records linked automatically.
BuilderBuddi: Open the job and create a quote from within it so the link is automatic.
4
Invoice from the job
When a milestone is reached, create the invoice from the job context so payment and delivery are always connected.
BuilderBuddi: Use the job page to trigger invoice creation.
5
Notebook and calculators feed the job
Site notes and calculator results should be saved and linked to the relevant job so nothing gets lost between site and office.
BuilderBuddi: When adding a notebook entry, link it to the job it belongs to.
BuilderBuddi workflow cards
Map your current jobs to the correct workflow
Pick one active job and verify every stage is connected — client, job, quote, and invoice all linked properly.
Jobs
Open job and check all links
Notes, quotes, and invoices all connected to the job
Review recordNotebook
Link any unlinked notes to their job
Context stays retrievable when needed
Start taskScattered records across separate menus
Context: A tiler has quotes in Quotes, notes in the notebook, and invoices in Invoices — but none are linked to a job. When the client disputes a charge, he cannot find what was agreed.
Challenge: How to clean up disconnected records and build the right habit going forward.
Recommended response: Create a job for the work, link the existing quote and invoice to it, and attach the relevant notebook entries. Going forward, always start from the job.
- • Create the job record if it does not exist
- • Link the existing quote to the job from the job page
- • Link relevant notebook entries to the job
- • Always create quotes and invoices from within the job going forward
Field notes
- • Jobs are the center of the operating loop — not quotes, not invoices.
- • Documents and notes support jobs; they are not standalone records.
- • Start from the client, not from the quote or invoice.
- • A job readable in two minutes is a job you can defend and hand off.
- • Every note captured on site should be linked to a job by end of day.
Key takeaways
- Jobs are the operating center — everything else connects to them.
- Client → Job → Quote → Invoice → Payment is the correct work loop.
- Notebook and calculators are upstream tools that feed job context.
- Unlinked records are invisible records — they exist but cannot be found when needed.
Common mistakes
Creating quotes or invoices without a parent job
Consequence: Records become disconnected. When a client asks a question about a job, you cannot find the relevant context quickly.
Prevention: Always create the job first, then create quotes and invoices from inside the job. Same amount of time, everything linked.
Using the notebook without linking entries to jobs
Consequence: Notes sit as isolated text. Finding measurements for a specific job requires scrolling through everything.
Prevention: When creating a notebook entry, always link it to the relevant job. One extra tap makes every note retrievable by job.
Treating documents and records as separate admin
Consequence: The job record looks empty even though work is happening, making job reviews and dispute resolution much harder.
Prevention: Documents, notes, and tasks belong inside the job they relate to. The job page should be the single place to read what is happening.
Complete this in BuilderBuddi
Implementation checkpoint
Tick these only when the real business output exists. This keeps Blueprint tied to work done, not pages viewed.
0% complete
Decision point 1: When you create a quote, where do you typically start?
Decision point 2: What should a job record contain when work is complete?
Practical action
Pick one active job. Open it in BuilderBuddi. Check that it has a linked quote, at least one notebook entry, and a clear next action. Fix anything missing before the end of today.
Worksheet prompt
List three jobs currently in progress. For each one, note what is missing from the job record and assign yourself to fix it today.
Worksheets and templates
Job Hub Audit Card
ChecklistFast checklist for job completeness across all five workflow stages.
Ready for immediate use
BuilderBuddi action bridge
Audit one job hub now
Use the job page to confirm scope, linked documents, notes, and next actions are all visible in one place.
Next step