← All work

(Case study · Build · 2026)

Samurai Striping

Pavement contractor site where the quote happens on the page, not on a callback.

Role
Designed and built the site end to end
Year
2026
Type
New build
Samurai Striping screenshot

(Problem)

Pavement contractors quote by callback — the customer fills in a contact form, waits a day for a return call, and books whoever gets back to them first. Samurai wanted the number in front of the visitor while they were still on the site, for two audiences with nothing in common: a homeowner pricing one driveway, and a property manager pricing a lot with 300 stalls.

(My role)

Designed and built the site end to end — the React front end, both estimators, and the request pipeline that delivers an already-priced job to the owner's inbox.

(The hard part)

Residential and commercial price on completely different models. Residential is area-driven: square footage, times coat count, plus optional pressure washing and crack filling — with a length × width helper because most people don't know their driveway's area. Commercial is line-item: per stall, per handicap and oversized space, per linear foot of curb, per bollard, sign, and bumper block, plus fire lane and crosswalk areas. Two pricing models, one calculation and submission layer underneath.

(Result)

Both estimators are live and total in real time as the customer fills them in, with no deposit or card details asked for. Every request lands with its numbers already attached, so the first phone call is a scheduling call instead of a discovery one.
Visit live ↗
(Next case study)Pyramid