Starting Points
The work starts with the blocker, not a fake pricing table.
Some jobs need a short audit. Some need a cleanup sprint. Some need a real operations build behind the public site. I scope it after seeing the messy part.
1
clear blocker
3
starting shapes
0
pressure to buy a package
How I quote the work
I look at the current site, the follow-up path, the owner's constraints, and the kind of proof the business already has. Then I recommend the smallest useful scope before anything bigger.
Engagement Shapes
Three ways a project usually starts
The names are simple on purpose. They keep the conversation grounded in what needs to change next.
Smallest useful step
Site and lead-path audit
Use this when the business has a site, but the homepage, services, photos, quote path, or Google proof are not pulling their weight.
Typical outputs
- Mobile and desktop first-impression review
- Quote/contact path notes
- Prioritized cleanup list in plain language
Good when you need a decision, not a full rebuild yet.
Most common fit
Local cleanup sprint
Use this when a contractor, landscaper, restaurant, or service business needs a stronger digital front door quickly.
Typical outputs
- Homepage and service-page rewrite
- Visual proof and CTA cleanup
- Bilingual page or estimate-flow improvements when useful
Good when the business already has real work, but the site does not show it clearly.
Deeper system work
Operations build
Use this when the problem is bigger than the website: lead follow-up, records, dashboards, invoices, payments, or internal handoffs.
Typical outputs
- Workflow map before implementation
- n8n, dashboard, CRM, or payment handoff build
- Handoff notes, logging, and follow-up plan
Good when repeated admin work is costing more than the software would.
Visual Scope
What the first pass is looking for
The review is not just color and layout. It checks whether a real person can understand the business, trust it, and take the next step without friction.
No mystery package menu before the problem is understood
No automation before the manual process is clear enough to trust
No design pass that ignores mobile, contrast, keyboard focus, or the actual next step
Send the messy version.
A rough site, old photos, an awkward form, a missed follow-up path, or a process that only lives in texts. That is enough to scope the first useful move.