When Ari Bleemer began calling paving contractors, his sales department was a headset and a Google Sheet. There was no polished script. There was, however, a useful question: how does this business actually run? The people on the other end described a day held together by estimates, calls, paper work orders, text messages, whiteboards, accounting software, and the memory of whichever employee knew where everything lived. Each tool worked in isolation. The handoffs did not.
Bleemer had come from a different operating environment. He studied computer engineering at Georgia Tech, added a minor that joined engineering with business, and graduated in 2018. At Bain & Company he worked across management consulting and private equity, spending time around critical-infrastructure industries. The education was partly technical and partly observational: watch how information moves through a company, notice where it stalls, then ask what the delay costs.
Construction looked well served from far away. Procore handled the coordination needs of large general contractors. ServiceTitan, Housecall Pro, and Jobber addressed single-visit field services. Bleemer saw a neglected middle between them: self-performing specialty contractors that estimate a project, win it, schedule crews, do the work, document changes, collect payment, and learn whether the job made money. Calling all of that simply “construction” flattened the problem. A paving contractor did not need a generic construction database. It needed its own operating sequence.
01 / The overlooked middleThe joke that revealed the opportunity
When Bleemer told his parents that he was leaving Bain to build paving software, they asked how quickly he was going to run into the mob. It was a family joke with strategic value. Paving was visible everywhere and understood almost nowhere outside the trade. Roads, parking lots, sidewalks, and driveways were part of daily life, yet the companies laying them were absent from most software conversations.
The joke also captured the skepticism Bleemer heard from friends, colleagues, and investors. Traditional industries, they told him, did not want new technology. Contractors were stuck in the past. Bleemer's calls produced a different diagnosis. Many operators had already bought software. They had been promised custom systems for five-figure prices and received tools that were awkward, incomplete, or unusable. Adoption was not blocked by an allergy to change. Trust had been spent by vendors who did not understand the work.
“People don't resist change. They resist wasting time and money on things that don't work.”Ari Bleemer
That distinction shaped OneCrew, the company Bleemer co-founded with Max Kostow. Instead of asking contractors to rearrange themselves around a horizontal product, they built around a sequence the industry already recognized: lead, estimate, proposal, schedule, field work, invoice, payment, job cost. An estimate was not merely a document at the front. It carried assumptions about labor, material, equipment, geography, phases, and margin into everything that followed.
02 / Trust before scaleAdvisors who became customers
OneCrew's first dozen or so customers arrived through a mixture of relationships and cold calling. Bleemer has said two of the first 11 or 12 were straight outbound wins. Most of the others were people he initially contacted as advisors while he learned the industry. They explained the pain points, became friends of the business, and eventually bought the product they had helped inform.
This was customer discovery with consequences. Calling a contractor to learn is different from calling to force a demo onto a calendar. Bleemer discovered that owners of overlooked businesses often wanted to talk when the caller displayed genuine interest and enough fluency to ask specific questions. The exchange offered something scarce: attention to the actual machinery of their company.
The method stayed useful as OneCrew grew. Cold calling remained a channel. Trade shows concentrated potential users in one room. Word of mouth carried a different kind of proof: a contractor willing to put a reputation behind a recommendation. Bleemer also made a hiring choice around the same principle. Salespeople did not have to come from paving, but they had to care about the businesses they served. The job was not to push a product regardless of fit. It was to understand whether the product could help the operator build a better company.
Industry learning became part of onboarding for every employee, including engineers. New hires learned the vocabulary and the daily constraints facing contractors. That distributed context changed more than sales calls. An engineer who understands why a dispatcher is juggling crew locations and material arrivals can make a sharper product decision without waiting for an “industry expert” to translate.
“It feels like you guys actually get it, which there's no better compliment for us.”Ari Bleemer, on customer feedback
03 / The discipline of narrowPassing on the quick horizontal move
OneCrew's architecture was configurable. The original plan allowed for expansion from paving into adjacent project-based trades within a few years. At the World of Concrete show in Las Vegas, Bleemer tested the product with a broader group. Concrete contractors and companies in neighboring categories recognized pieces of their own workflow. Demand existed.
The company stayed focused on paving. Bleemer has been candid about the trade-off: the quickest route to early growth might have been collecting a couple dozen customers in several industries. The durable route was to become known in one. Every paving customer added a reference another paving contractor might trust. Every implementation deepened the team's vocabulary. Every trade show appearance made the company less of an outsider. Time in the market became part of the product.
Look between established platforms for operators managing a full workflow that neither product owns.
Begin with people who can correct your assumptions. A relationship built around learning can outlast a transactional pitch.
Make domain fluency part of every role. Context belongs in engineering and onboarding, not only in sales.
Measure a vertical by reference density, language, and trust as well as immediate revenue.
This is the less photogenic part of vertical software. Focus is not choosing a label for the home page. It is declining nearby revenue, sending engineers into domain education, and accepting that credibility accrues at the pace of consistent delivery. A configurable codebase can travel quickly. A company's reputation cannot.
04 / From clarity to capitalThe estimate becomes an operating record
OneCrew's product now spans CRM, estimating, scheduling, dispatch, mobile field management, invoicing, payments, and real-time job costing. The point is not that a contractor can buy many features from one vendor. The point is that the same job can keep its context as it travels through the business. A change in the field can reach the invoice. A schedule can remain connected to crews and materials. Actual margins can inform the next bid.
The company announced a $3.25 million seed round in 2024. In 2025 it raised a $7.5 million Series A led by Stage 2 Capital, with continued backing from Entourage and Bienville. Bleemer framed that financing around a larger operating ecosystem: enterprise tools, a subcontractor portal, and connections among contractors, crews, customers, and partners. He has also spoken about using AI sensibly, with reliable operating data underneath it rather than novelty sitting above a fragmented process.
His public writing returns often to information quality. Contractors considering another crew need to know where margin is made, which services perform well, and where a job quietly loses money. Without reliable data, adding people feels like a wager. With a record of estimates and actual costs, the choice can become an operating decision. The software matters because the decision matters.
05 / What the asphalt teachesA company built around the handoff
Bleemer's route from computer engineering to consulting to paving has a clean thread: systems. Georgia Tech taught the machinery. Bain offered a view across businesses and industries. OneCrew turned the observation toward companies whose machinery was physical but whose information system was improvised.
The founder lesson is more grounded than “pick an unsexy industry,” a phrase that tends to make the industry sound like a prop. Paving contractors were not waiting to play a supporting role in a software story. They were running complex, seasonal, capital-intensive businesses. Their skepticism contained product requirements. Their paper trails contained a data model. Their willingness to explain the work gave Bleemer a map, provided he listened long enough to read it.
That map still leads through the handoffs: sales to operations, office to field, completed work to billing, actual cost back to the next estimate. OneCrew's bet is that clarity at those seams can change how a contractor grows. Bleemer's own bet was that a narrow market could reward patient attention. The roads were always there. The opportunity was learning to see the business moving across them.