Work
Selected work, by vertical.
Described by vertical, not by name. Client names appear only with written permission, and each entry covers what was built and what changed structurally rather than what it earned.
Regional roofing contractor
Rebuilt lead intake and routing across paid, organic, and call channels. Single pipeline, sixty-second first touch, owner dashboard replacing a whiteboard.
Evidence boundary: shipped architecture and operating path. No revenue claim published.
IntakeRoutingReportingMulti-location senior living operator
Consolidated tour requests from four property sites into one pipeline with per-location routing and occupancy reporting the regional director reads without asking anyone.
Evidence boundary: consolidation and reporting structure. Occupancy outcomes are the operator’s to publish.
CRMMulti-locationReportingTelehealth practice
Built intake and scheduling infrastructure with automated eligibility checks, structured handoff to clinical staff, and no protected health information passing through marketing tooling.
Evidence boundary: intake architecture and data-handling design. No clinical or volume claim.
IntakeSchedulingData handlingIndependent jewelry retailer
Shopify rebuild with server-side conversion tracking, catalog restructure, and recurring invoicing for custom orders that had been running on emailed PDFs.
Evidence boundary: platform rebuild and billing path. No conversion-rate or sales claim.
CommerceTrackingInvoicingStart
Start with what’s broken.
Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.
Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.
Or email hello@strygon.com
- What to send
- A paragraph. What broke, and where it shows up.
- What comes back
- A read on what is likely wrong and what fixing it takes.
- Price
- The last conversation, not the first