Founder
Payton Ward
Founder, Spillway
I built Spillway around a simple observation: roofing companies spend a lot of money getting homeowners to call, but perfectly legitimate situations disappear when somebody is not ready to book during that exact conversation.
That never made much sense to me.
Spillway Calls keeps those conversations alive without creating another workflow for the roofing company.
In the early days of Spillway, I think it matters that contractors know exactly who is behind what they are connecting to. My name is on it, and I want the company to be unusually straightforward about what the product does, what access it needs, how billing works, and where the limits are.
Why I built Spillway Calls.
A legitimate roofing situation can disappear because one call ended before the homeowner was ready to book. Spillway continues appropriate conversations under the contractor’s name, coordinates available inspection times with the office, and returns the confirmed time for the team to schedule.
How I think about Spillway
The product can be surprising. The company should never be mysterious.
If Spillway makes an extraordinary claim, I want there to be an exact mechanism and exact proof behind it.