Calculators
Run margin check on a recent job
Establish real margin baseline for rule-setting
Start taskBlueprint journey
Lesson 5 / 36
0 completed
Next best lesson: Start Here: How to use Blueprint week by week
Guided operating lesson
Think like an operator, not only a tradesman
Use business logic to protect the quality of your trade work and your time — instead of just taking every job that calls.
Business Foundations12 minFoundational
Who this is for
Skilled tradespeople who are excellent at the work but find the business side chaotic, reactive, or consistently unprofitable.
Why it matters
Trade skill and business skill are different capabilities. You can be outstanding at the work and still run a business that is financially fragile, stressful, and impossible to grow.
Lesson outcome
You have three clear job acceptance rules and a weekly decision rhythm that filters work before it enters your schedule.
Real-world problem
Being busy is not the same as being profitable or in control.
Most skilled tradespeople grow their business by saying yes to almost everything and working harder when things get tight. This creates a ceiling — the business grows to the capacity of one person's effort, and any slack creates immediate cash pressure. The operator mindset breaks this by applying business logic to every job decision before it is accepted.
A painter books himself three months ahead but takes home less than he made as an employee. He is busy but every job has weak margin, difficult clients, or scope that expanded without variation charges.
Why this happens
Trade identity is built around doing great work, not filtering it
Most tradespeople are trained to take pride in their craft and serve clients well. Saying no to work or declining a client feels like a failure of that identity. Business logic that should filter decisions gets overridden by the tradesperson identity.
No explicit acceptance rules exist
Without defined criteria for what work to accept, every enquiry gets evaluated emotionally in the moment. Some slow weeks feel desperate and almost anything gets accepted. Neither approach is systematic or reliable.
Professional standard
Score every job before saying yes
An operator evaluates every job on at least three criteria before committing: minimum acceptable margin, scope clarity at enquiry stage, and payment terms agreed. Any job that fails two or more criteria gets a harder look before acceptance.
A weekly decision rhythm replaces reactive responses
Schedule a weekly planning review where work pipeline, job margins, and upcoming resource needs are reviewed together. This prevents the panic-accept/over-commit cycle.
Step-by-step operating system
Define and apply your job acceptance rules
1
Define minimum acceptable margin
Set a floor — below this margin, the job is not worth the risk and overhead unless it is strategic.
BuilderBuddi: Use Calculators to run the margin check on a recent job and establish your current actual margin as a benchmark.
2
Define minimum scope clarity
What level of scope definition do you require before committing a price? A site visit before quoting commercial jobs, for example, is a scope clarity rule.
3
Define payment terms as non-negotiable
Set your deposit requirement, payment schedule, and overdue terms before any job starts.
BuilderBuddi: Open Settings and verify your payment terms are visible on your quote and invoice documents.
4
Apply the rules at enquiry stage
When a new enquiry comes in, run it against your three rules before responding with a quote or booking a site visit.
BuilderBuddi: When creating a new job, add a note about which acceptance criteria were checked.
5
Run a weekly pipeline review
On Monday, review your active jobs, pending quotes, and upcoming enquiries against your rules.
BuilderBuddi: Use the dashboard and jobs list as the surface for your weekly operator review.
BuilderBuddi workflow cards
Build your acceptance rules into the job workflow
Use calculators to verify margin and the job record to track which criteria were checked before acceptance.
Jobs
Add acceptance notes to new job enquiries
Record which criteria were met before committing
Start taskDashboard
Weekly pipeline review
Catch rule violations before they become booked jobs
Open in BuilderBuddiThe job that seemed fine until it was not
Context: A tiler accepts a residential renovation job because the client seemed nice and the work was nearby. Scope was vague, margin was thin, and payment terms were never discussed. Two months in, the job has three disputed variations and a final invoice unpaid.
Challenge: How to prevent this pattern by applying acceptance rules at enquiry stage.
Recommended response: At enquiry, run the job against three rules: margin check, scope clarity check, and payment terms confirmation. If any two fail, the job requires a harder conversation before acceptance.
- • Before booking a site visit, confirm client has a clear scope in mind
- • Before sending a quote, run the margin check in Calculators
- • Before starting work, confirm deposit and payment terms in the job record
Field notes
- • Trade quality and operating quality are completely different capabilities.
- • Saying yes to every job is not confidence — it is the absence of a filter.
- • A job that fails your margin, scope, and payment criteria will cause problems later.
- • Weekly planning review prevents the panic-accept/over-commit cycle.
- • Your acceptance rules are worth more than any single job you might lose by having them.
Key takeaways
- Define three job acceptance rules: minimum margin, scope clarity, and payment terms.
- Score every enquiry before committing to a site visit or a price.
- A weekly planning rhythm replaces reactive yes/no decisions under pressure.
- Operator decisions protect your trade quality — they do not conflict with it.
Common mistakes
Accepting jobs without any margin or scope check
Consequence: Jobs with weak margin and vague scope become the jobs that cause the most stress, rework, and payment disputes.
Prevention: Run three quick checks before any enquiry becomes a booked job: margin floor, scope clarity, and payment terms agreed.
No weekly review of the work pipeline
Consequence: The business swings between over-committed and under-committed with no early warning. Cash flow becomes unpredictable.
Prevention: Block 30 minutes Monday morning for a pipeline review. This single habit prevents most reactive business decisions.
Treating payment terms as something to raise after work starts
Consequence: Once work has begun, payment term negotiation is uncomfortable and often fails.
Prevention: Include deposit requirement and payment schedule in every quote. Confirm before starting.
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: Do you have written job acceptance rules you apply consistently?
Decision point 2: Do you review your active work pipeline at the start of each week?
Practical action
Write three job acceptance rules right now: minimum margin percentage, minimum scope clarity at enquiry stage, and payment terms required. These become your filter for every new enquiry from today.
Worksheet prompt
Write your three acceptance rules and where they are visible in your workflow. Then list the last three jobs you took and score each against the rules.
Worksheets and templates
Job Acceptance Rules Sheet
TemplateDefine and document your minimum criteria before committing to any job.
Ready for immediate use
Next step