200 Meetings Before One Line of Code
Most startups in construction technology were built by outsiders with a thesis. Ramdas had a thesis too - but he stress-tested it with a method borrowed from the best customer-success playbooks he'd written at Strikedeck and Medallia.
He hired a full-time SDR before the product existed. Authorized a budget that would make most early-stage founders wince: roughly $200,000. The job was simple: get Ramdas in front of 200 construction firms. Not to pitch. To listen.
Those 200 conversations shaped every product decision Lumber made in its first two years. They revealed that the problem wasn't just payroll - it was the entire operating model of the back office. It was the certified payroll reports that had to be filed in 12 different county formats. It was the prevailing wage audits that required reading collective bargaining agreements the size of phonebooks. It was the paper timecards that were faxed in on Monday mornings and had to be manually transcribed before anyone could run payroll.
When Ramdas talks about Lumber's AI being designed for real workflows rather than ideal ones, that's where it comes from. Not a whiteboard. Two hundred conversations with the people who actually do the work.
Viewing failure as data and maintaining velocity during uncertain times.
- Ramdas on his operating philosophy