Tech loop
Open the app, find the path, save the proof, and say whether it helped, missed, or needs more data.
Why this wins
The route app owns the schedule. SplashLens owns the stuck moment.
The market already has route, billing, CRM, and homeowner-portal tools. SplashLens should own the moment a tech is standing at equipment with a code, weird part, unclear symptom, or facility question and needs a safer next move.
1
Identify
PartSnap and lookup return possible equipment families, proof gaps, and next verification steps.
2
Prove
Photos, readings, model plates, labels, symptoms, and missing evidence become a cleaner job record.
3
Send
The tech can hand off the right details to a senior tech, supplier, manufacturer support, trainer, or customer.
4
Learn
Real misses become short field lessons, partner cards, and owner-visible coaching signals.
The network effect
Every useful stop should make the next stop faster.
The moat is not a generic chat box. The moat is structured field memory: what was searched, what proof was missing, what part family was likely, what got sent, what came back, and what should be taught next.
Counter loop
Before ordering, ask for model plate, second photo, old part markings, symptom, code, and fit clues.
Partner loop
Manufacturers and trainers can provide known failure points, model families, docs, and preferred field-safe language.
Business model
Free for the tech. Paid when proof, training, or review matters.
The trust move is to keep core lookup useful. The revenue starts when a company needs saved history, team visibility, training, facility access, verified cards, or cleaner support flow.
Free Core$0
Lookup, calculators, basic PartSnap, notes, and field reference.
Solo Proof$19 target
Saved job trails, customer-safe notes, and proof packets.
Team Network$99+ target
Owner dashboard, repeat misses, saved proof, and coaching signals.
Partner CardsCustom
Manufacturer, distributor, facility, and training workflows after real review.
Verification boundary: a card is only marked partner-verified after a real partner supplies and approves the language. Until then, SplashLens uses possible matches, missing-proof prompts, and manual verification language.
Moonshot build map
The product chases one measurable moment.
A tech opens SplashLens, finishes one real field task, and says: that saved me time. Everything else exists to repeat, prove, and monetize that moment without pretending the app is a diagnosis authority.
Live field loops
PartSnap, lookup, scan events, feedback taps, saved proof, share prompts, and article/referral attribution are wired for activation proof.
Source-backed PartSnap
PartSnap separates AI-only clues from source-backed family candidates, then asks for the next proof photo before ordering.
Partner-gated verification
Manufacturer, distributor, trainer, and facility cards stay unverified until a real partner supplies and approves the language.
Native parity lane
iOS and Android should mirror the latest web front door, conservative ASO, screenshots, and free-core store disclosures.
Next unlock: turn named pilots into proof. Track 25 techs, 5 companies, and 3 facility/training groups through one assignment: try a real code, part, facility issue, spa stop, or proof packet and tell SplashLens whether it helped, missed, or saved time.