Local entry point
A focused start page explains who the experience serves and the types of home projects it can help route.
Working case study | Metro East, Illinois
All Pro Metro East: Project Match by Bill
How Bill Session's local contractor knowledge became a public customer path that FieldKnown could structure, build, and extend.
Current design captures and documented scope for Metro East Project Match by Bill. No traffic, ranking, lead, job, or revenue result is claimed.
Working context
Metro East, Illinois
Operator input
Bill Session
System builder
FieldKnown
Public status
Live and evolving
The design challenge
Turn local judgment into a customer path people can use.
Bill knew the service area, the project fit, and how a useful first conversation should work. The website needed to carry that knowledge without pretending every homeowner request already belonged to one contractor or a finished referral network.
The path had to
Start with the homeowner's project
Collect only useful routing context
Keep the next action understandable
The path could not
Act like a fake directory
Hide future referral economics
Promise an unmeasured outcome
What was built
Four connected parts, one understandable next move.
Plain-language intake
Homeowners begin with the project, city, budget, timing, and kind of help they want instead of choosing from internal business categories.
Transparent routing
The page explains the current All Pro first lane, possible future referrals, and how paid participation would be disclosed.
Reusable operating path
Useful local content, project proof, intake, and routing can now improve together instead of living as disconnected website tasks.
Real project source material
Real project work makes the customer story specific.
Bill supplied operating context and actual All Pro project photography. FieldKnown used that kind of owner-provided evidence to make the public story specific instead of relying on stock-like visuals or invented jobs.
These client-supplied photographs document the project types available to the website build. Performance measurement is outside this case study.
The work, not a mockup
The same path on desktop and in a homeowner's hand.
These captures document Metro East Project Match as reviewed on October 1, 2026. Use the source link below to inspect the live page as it continues to evolve.
Verified public-page observations
Evidence that is public and inspectable.
Checked against the public project-match page. These observations concern the visible interface. No form was submitted and no lead delivery or business outcome was tested.
The public start page is live and can be inspected directly.
The customer path uses project language instead of software language.
The page provides links to its privacy policy, terms, and referral disclosure.
The page identifies All-Pro as a direct response option and explains permission-based sharing with participating contractors.
The form asks for project details and explicit contact and sharing consent.
Unknown: measured outcomes
Results still require measured evidence.
Screenshots reviewed October 1, 2026. The linked public page is the source for the current wording and interface.
Search-visibility change is not reported.
Lead, appointment, and project volume are not reported.
Collected revenue is not reported.
Contractor-network adoption is not reported.
Roles kept clear
Operator judgment leads. Technology supports it.
Bill's role
Define the local customer, service fit, routing reality, and trust boundary.
FieldKnown's role
Turn that knowledge into public structure, useful content, intake, and a visible next action.
Technology's role
Help organize and improve the system without inventing promises or replacing owner approval.
Bring one stuck customer path
Start with the part customers or employees should understand better.
A private growth review can identify whether the next move is a website fix, clearer intake, better follow-up, or an owner-approved operating playbook.