Jobs
Select sprint job and verify it is complete
One job with scope, notes, and next action clear
Start taskBlueprint journey
Lesson 4 / 36
0 completed
Next best lesson: Start Here: How to use Blueprint week by week
Guided operating lesson
First 7-day wins
Create visible business improvement in your first week without trying to change everything at once.
Start Here18 minFoundational
Who this is for
Contractors who want to start the course with real momentum rather than a week of planning with nothing to show.
Why it matters
Early visible wins prove the system is working and create the motivation to keep applying lessons. Without them, the course becomes another good idea that gets shelved.
Lesson outcome
You have completed one clean end-to-end job flow and have a concrete result to measure against.
Real-world problem
Week one feels productive but produces nothing measurable.
The first week of any new system tends to be spent reading, planning, and setting up rather than doing. This creates a lot of positive feeling but no actual change in how the business operates. The first real test of whether anything has changed is whether a specific job is running better than it was before.
A tiler spends his first week setting up folders, reading the full course, and writing goals. By Sunday he has impressive notes but no quote sent faster, no invoice followed up, and no job running any differently.
Why this happens
Preparation feels like progress
Setting up systems and reading content feels like valuable work. But until an action is taken inside a real job, nothing has actually changed. The preparation phase can expand to fill any amount of time.
No specific target defined for week one
Without a named job, a named action, and a named result to check at Friday, week one defaults to general exploration. Exploration produces learning but not business improvement.
Professional standard
Run one clean loop end to end
The goal for week one is simple: take one job through a complete flow — capture notes, create quote, send quote, create invoice, follow up on payment — with timestamps at each stage. This proves the system works.
Close open loops — anything stalled for seven days or more gets reviewed
While running your clean loop, audit anything stuck in the system. Quotes not sent, jobs with no next action, invoices overdue. Closing one stuck item is as valuable as starting a new clean loop.
Step-by-step operating system
Seven-day execution sprint
1
Pick one live job as this week's target
Choose a job currently in progress or just starting. This is your sprint vehicle for the week.
BuilderBuddi: Open Jobs, find one active job, and confirm it has a client record, scope description, and at least one task.
2
Capture site notes and link them
Before or during your next site visit for this job, capture notes in the notebook and link them to the job.
BuilderBuddi: Create a notebook entry for the job and link it. Write measurements, scope observations, or access notes.
3
Create and send the quote
If a quote is pending, build it using the correct structure and send it within this week. Track the time from site visit to quote sent.
BuilderBuddi: Create the quote from inside the job. Review before sending. Note the total time taken.
4
Create and send the invoice at the right trigger
When the milestone or completion trigger is reached, create and send the invoice the same day.
BuilderBuddi: Create invoice from the job when the trigger is hit. Send with a clear payment due date.
5
Follow up on payment if overdue
If the invoice passes its due date without payment, send one professional follow-up within 24 hours.
BuilderBuddi: Check invoice status. If overdue, send a follow-up with the due date context.
BuilderBuddi workflow cards
Run your first complete business loop
Use jobs, notebook, quotes, and invoices together on one job this week to prove the system works end to end.
Quotes
Create and send quote from within the job
Quote sent within target turnaround time
Start taskInvoices
Send invoice at the right trigger and follow up
Invoice sent same day as trigger, followed up if overdue
Start taskWeek one with nothing to show
Context: A roofer reads all four Start Here lessons in a day, sets up his profile, and browses the calculators. By Friday he has not changed a single job action.
Challenge: How to redirect the first week toward a visible, measurable result.
Recommended response: Pick one job currently in progress. By Friday: site notes linked, quote sent or invoice followed up. That single action loop is the entire goal for week one.
- • Open Jobs and pick one active job as the sprint vehicle
- • Add or link at least one notebook entry to it
- • Send one pending quote or follow up on one overdue invoice
- • Record the time from note to quote, and from invoice sent to follow-up
Field notes
- • Week one success is measured in one completed loop, not in lessons read.
- • Quick wins prove the system works and create the motivation to keep going.
- • Anything stuck in the system for seven days or more needs a decision today.
- • Time your loop — note to quote, invoice to follow-up. These become your baseline.
- • Completion beats expansion in week one every time.
Key takeaways
- Run one complete job loop this week — notes, quote, invoice, follow-up.
- Time each stage so you have a baseline to improve against.
- Close at least one stuck item — stalled quote, overdue invoice, or job with no next action.
- Visible results in week one create the motivation that keeps the course practical.
Common mistakes
Spending week one only reading and planning
Consequence: By end of week one, nothing in the actual business has changed. The course is still just a good idea.
Prevention: Assign a specific job and a specific loop to complete before Sunday. Reading is valuable only when it leads to an applied action.
Starting multiple process changes at once
Consequence: No single change gets completed cleanly, momentum stalls, and it becomes hard to tell what is working.
Prevention: One loop, one job, one week. Complete the clean loop before expanding to other improvements.
Ignoring existing stuck work in favour of new process setup
Consequence: Stalled quotes and overdue invoices keep costing money while you build new systems.
Prevention: Before starting your clean loop, do a 10-minute audit: clear or close any quote, job, or invoice stuck for more than seven days.
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: Have you identified the one job that is your week-one sprint vehicle?
Decision point 2: Do you know your current quote-to-send turnaround time?
Practical action
Open Jobs now. Pick one active job. Write its name, the one action you will complete on it this week, and the day you will check whether it is done. Do not close BuilderBuddi without doing this.
Worksheet prompt
Record the sprint job name, the action, and the target completion day. On Friday, record whether it was done and how long the loop stage took.
Worksheets and templates
7-Day Execution Sprint Board
TemplateTrack one complete business loop from notes to payment this week.
Ready for immediate use
BuilderBuddi action bridge
Run your sprint in BuilderBuddi
Use jobs, quotes, and invoices to complete one end-to-end business loop this week and time every stage.
Next step