Roofing + skylight decision system
JB’s Roofing
Weather Out. Daylight In.
Roofing, skylights, or help deciding. Those three starting points make JB’s Roofing / Central Coast Skylight Solutions easier to explore before the first conversation.
- Google Maps 4.8 · 24 reviews
- Snapshot checked Sep. 6, 2026
- No website attached to Maps
- 1356 Breck St · SLO
The website, redesigned
Explore the concept site.
Use the preview below to try the pages and tools. For more room, open the concept site in a new tab.
For developers
Download source code
Reimagined local launch
A roof concern or a brighter room?
Keep both business names, then ask what the homeowner needs: weather protection, more daylight, or help considering both. Carry that choice into the brief, estimate, and vehicle graphics.
Translate roofing and skylight complexity into a legible, photo-supported assessment path.
People responding to a concern, planning an improvement, or unsure which specialist they need.
Share issue type, timing, property context, and photos without receiving a remote promise.
A pitched protective line opens into a square of daylight across every format.
Website, print, signs, and vehicles.
Protect the roof. Open the room.
Begin with weather, daylight, or “I’m not sure.” Add context and photos for a structured assessment request, not an online diagnosis or quote.
Dry above. Bright below.
Roof + light, one clear assessment.
Dry above and bright below. Open the outdoor concept detail.What does the room need overhead?
The vehicle’s own roof becomes the canvas for a storm-to-daylight transition, readable without a dense service list.
Launch plan
- Phase 01 · Verify
Resolve the operating truth
Confirm business naming, services, licenses, permits, warranties, service area, scheduling, emergency availability, materials, and authoritative contact routes.
- Phase 02 · Frame
Test the three-door intake
Prototype weather, daylight, and unsure paths with real customer questions; connect the site, report, mailer, signs, and fleet to one vocabulary.
- Phase 03 · Illuminate
Launch with verified project evidence
Add consented exterior/interior project pairs, accurate scope notes, and date-stamped operational details under a named content owner.
Three large choices lead to an accessible assessment form, process explanation, verified evidence, and one canonical contact record.
Roofing and skylight language, identity, phone, location, service area, and licensing references stay reconciled across every public profile.
“Dry above. Bright below.” identifies the system while project-specific information appears only with owner and homeowner approval.
A weather/daylight foldout helps recipients recognize which conversation to start without manufacturing urgency or fear.
An annotated Roof + Light Report separates verified observations, photos, options, dependencies, and customer-approved next steps.
A roofline aperture wraps the actual body geometry; road-speed copy stays minimal and a deeper path appears only where safe when parked.
A hypothetical cutaway lab becomes operator-approved educational content about questions, layers, and daylight placement, not DIY repair advice.
A modular assessment deck and project recap use the same roof/light choice so the handoff does not restart from zero.
Storm outside, daylight inside.
Midnight blue, cloud ivory, galvanized gray, rain blue, and one skylight yellow. Exterior protection and interior light appear as paired frames. The voice is plain, measured, and non-alarmist: “Tell us what you notice overhead.”
Measure which doorway earns a real assessment.
- Website, three-door intake, identity architecture, jobsite signs, foldout, report, cutaway kit, sales deck, and vehicle-family templates.
- Before production: verify licensing, services, permits, emergency scope, service area, materials, warranties, contacts, and image permission.
- Measure path choice, completed assessment requests, qualified calls, photo uploads, directions, and roof-versus-skylight demand mix.
Brand kit
Open the kit for editable logos, social graphics, print layouts, and vehicle artwork. The guide explains colors, type, spacing, and production checks.
Explore the full brand kit →Download identity files ↓Palette
Paper #FFF9EB, ink #10233A, action #FFD75C, supporting #78909C. Use ink on paper for body copy; the downloadable color file includes tested contrast pairs.
TypographyWeather out. Daylight in.
Display: Georgia, serif. Body: Arial, sans-serif. System-font stacks; no proprietary font files are bundled.
Graphic deviceThe roof aperture
A simple roof encloses a daylight opening. Preserve the aperture and surrounding negative space; do not fill it with photography at small sizes.
Voice + imageA brighter outlook. A sound roof.
Reassuring and practical. Treat protection and daylight as two clear customer needs.
Roof planes, flashing details and daylight entering rooms. Use documented job photos with permission and captions.
Open every artifact
01 · Website Weather, daylight, or unsure
The home page begins with intent and progressively asks only the questions needed for a useful follow-up.
- Content: need, property context, timing, issue location, optional photos, and reply preference.
- Production: accessible upload, clear errors, confirmation, privacy, and real workflow routing.
- Constraint: no diagnosis, price, availability, or emergency promise is automated.
02 · Jobsite + outdoor Dry above. Bright below.
The binary message works at distance while details remain with the stationary project sign or verified destination.
- Content: one line, business identity, approved project category, and contact path.
- Production: permits, sightlines, wind, reflectivity, installation, and removal plan.
- Constraint: property use and project descriptions require approval.
03 · Direct mail Roof + light decision foldout
The foldout opens from an exterior roof plane to an interior daylight field and ends with three request paths.
- Content: observation prompts, decision questions, verified service fit, and one current route.
- Production: postal-safe construction, household segment codes, and web equivalent.
- Constraint: no invented seasonal discount or fear-based safety claim.
04 · Field card Roof + Light assessment record
A compact record connects each photo or observation to a location, category, and next-step status.
- Content: observed condition, roof/light/both tag, dependency, option, and follow-up.
- Production: weather-resistant field version plus accessible digital recap.
- Constraint: terminology and record status require operator and legal review.
05 · Demonstration Roof + Light Lab
A portable cutaway makes hidden layers and daylight decisions discussable without climbing a roof.
- Experience: layer labels, question prompts, daylight aperture, material handling, and consultation path.
- Production: safe concept construction, modular signs, captions, handout, and follow-up.
- Constraint: hypothetical activation only; no event or material endorsement is announced.
06 · Measurement Choice-to-assessment signals
The plan tests whether the three-door architecture routes people correctly rather than promising lead volume.
- Primary: path choice, completed requests, qualified calls, uploads, and directions.
- Quality: misrouted needs, incomplete fields, response gaps, and assessment outcomes.
- Governance: baseline, consent, retention, attribution, and reporting owner set first.
07 · Fleet + vans Storm-to-daylight roofline
The wrap uses the actual vehicle roof to separate protection from light while preserving legibility and service access.
- Side: roof aperture, short line, identity, and verified contact route.
- Rear/parked: approved categories and safe scan zone if operationally useful.
- Production: templates by vehicle, seam avoidance, reflectivity, proof, and installer handoff.
Public footprint snapshot checked September 6, 2026: Google Maps profile and public directory profile. Maps showed 4.8 from 24 reviews and no website action; the directory independently corroborated the business identity and showed 23 reviews when checked. A current license, exact services, and all operating claims would need direct validation before production.