A construction invoice can be perfectly accurate and still become difficult to collect. The work may be finished. The concrete may already be curing. But a preliminary notice went to the wrong owner, a lien deadline expired, a waiver released more than the supplier had been paid, or the person reconciling the check could not match it to the right project. In most industries, this is clerical drag. In construction, paperwork can decide whether a company keeps its legal leverage to get paid.
Handle.com built a business inside that distinction. The San Francisco company sells software to the credit and finance teams at material suppliers, equipment dealers, distributors, contractors and subcontractors. It links lien and notice management, waiver exchange, credit operations and online payments. The pitch is less about replacing an accounting system than supplying the construction-specific logic that generic finance software leaves out.
That logic has become a sizable data trail. Handle says more than $160 billion in invoices and financial workflows have passed through its platform. Its named customers include Ferguson, Cemex, ABC Supply, Floor & Decor, EquipmentShare, US LBM, Heidelberg Materials and units associated with The Home Depot. In May 2026, the company raised a $27 million Series B after nearly doubling contracted annual-recurring-revenue bookings over the prior six months.
The clock is part of the product
Handle's founding insight came from close range. Co-founder and CEO Patrick Hogan grew up around his family's lumber business. Slow payment was not an abstract market inefficiency; it constrained what suppliers and contractors could do next. When TechCrunch profiled Handle in 2020, Hogan described a contractor waiting more than a year on a $200,000 hotel invoice. Co-founder Chris Woodard put the limit plainly: contractors could grow only as fast as they got paid back.
The first version of the story mixed workflow software with working capital. Handle had raised $4.5 million in known venture funding and arranged $20 million in debt financing to support businesses waiting on checks. Just as important, the founders designed around a problem that kills many enterprise products: needing both sides to agree. The party waiting for payment could use the early system without persuading the payer to adopt it first.
“It only requires the party who is going to be receiving the payment to use it.”Patrick Hogan, describing Handle's early adoption strategy
That was the original trick. The larger opportunity appeared as customers pulled Handle deeper into their operations. A notice depends on correct job information. The waiver depends on the amount and payment status. The payment affects the waiver. The invoice, property, contractor, owner, deadline and release are not separate objects merely because five software products treat them that way.
Handle's claim to usefulness lives in the arrows. Break those links and the credit team returns to email, spreadsheets and duplicate entry.
What failed first: the spreadsheet
The clearest evidence comes from U.S. Concrete, whose distributed credit divisions once verified owners and tracked payment deadlines manually. That meant repetitive research, spreadsheet calendars and project information entered in more than one place. The visible failure was wasted time. The dangerous failure was less theatrical: the wrong party or a missed statutory date could weaken payment rights.
Handle automated owner verification, deadline calculation and alerts as unpaid invoices approached critical dates. It also provided an audit history across teams. Credit staff could spend the recovered time on collection rather than copying data. Terry Marshall, then U.S. Concrete's chief innovation officer, said the company had examined alternatives but found something in Handle it could not find elsewhere.
Elite Roofing Supply offers the less polished, more useful version of the lesson. One county office could not process a filing near the end of a 90-day window because an employee was unavailable. The credit team responded by building 14 to 20 days of buffer into filing decisions, depending on project size and customer risk. Software can display the deadline; competent operators still leave room for the human system around it to fail.
From compliance wedge to finance layer
The product now has four main doors. Lien and notice management researches owners, contractors and lenders, then tracks deadlines and supports filing. Waiver management generates statutory or custom forms, calculates amounts, validates signatures and preserves an audit trail. Credit tools collect job sheets and synchronize project data. Payments handle cards and ACH while connecting the transaction to invoices, waivers and lien status.
The payments side has expanded into receivables work: automated cash application, short-payment and deduction identification, trade-credit memos, pre-pay invoices and ERP updates. The contractor-facing portal is free and mobile-friendly. That choice echoes the founders' early thinking. If the payer needs procurement, training and a new subscription before sending money, adoption stalls. Remove the login and the extra bill, and the supplier's software becomes easier for its customer to tolerate.
Generic payment stack
- Sees payer, amount and settlement
- Leaves waivers in another workflow
- Knows little about state lien clocks
- Pushes project context back to the ERP
Handle's construction stack
- Links payment to invoice and project
- Connects waivers and lien releases
- Applies jurisdiction-specific rules
- Keeps an audit trail across the chain
This is also how Handle distinguishes itself from specialist competitors such as Levelset, a Procore company, and from broader receivables platforms. Levelset is a recognizable alternative for lien rights and payment documents. Generic AR products can be stronger across ordinary business payments. Handle is betting that large suppliers want the construction rules, expert research, filing service, waiver exchange and payment flow under one roof.
It is an enterprise sale, not a swipe-a-card subscription. Handle does not publish list prices and directs buyers to demos. The business appears to combine vertical SaaS contracts with payment-processing economics and managed services such as project research, filing, onboarding, training and account support. That service layer matters when the software's answer can affect a legal right and when a national supplier must configure different rules across branches.
The funding follows the widening workflow
Handle joined Y Combinator's Winter 2019 class. Its $10 million Series A arrived in March 2022, led by Energize Ventures and Ironspring Ventures, to expand support, engineering and sales. At the time, the platform held roughly $4.8 billion across two million invoices. Fiserv payment technology followed in 2023. Amex Ventures and Suffolk Technologies made strategic investments in 2024.
The 2026 Series B, led by Marbruck with Energize, Suffolk, Liquid 2, RXR and WEX participating, is meant for payments infrastructure, compliance automation, collections and AI-driven workflows. The company's “construction data graph” is the strategic center of that plan: join parties, projects, invoices, documents, deadlines and payments, then let software reason across the connections.
There is real promise and an obvious condition. AI is useful here only if the underlying project records are accurate, current and legally mapped to the right jurisdiction. A confident model sitting on bad owner data would automate the wrong notice faster. Handle's continued investment in manual verification, expert audits and state-specific rules suggests it understands that the graph must earn trust before the intelligence layer can spend it.
The playbook worth copying
Handle's growth offers a tidy vertical-software lesson. Start with a repeated task where the error cost is much larger than the labor cost. Make adoption possible for the party with the strongest pain. Integrate with the accounting system rather than demanding its replacement. Then follow the data into adjacent steps that customers already perform before and after the original task.
Borrow this, not the hard hat
- Find the deadline or rule generic software cannot model.
- Sell first to the person who loses money when it breaks.
- Remove adoption work for everyone on the other side.
- Connect adjacent records before adding “intelligence.”
- Keep experts in the loop where errors carry legal weight.
The same playbook will not work everywhere. A small contractor with a handful of local jobs, simple payment chains and little lien exposure may be perfectly well served by a calendar and disciplined filing habits. A buyer must have enough project volume, jurisdictional variety, payment friction or duplicate work to justify implementation. The economics become sharper when one missed deadline can expose a large receivable, or when dozens of employees each lose hours every week to the same manual routine.
Handle is now aimed squarely at that enterprise condition. The company that began by helping one side get paid is trying to own the connective tissue around the payment. If its thesis is right, construction's next financial system will not look like a generic processor wearing a work boot. It will know which project the money belongs to, which document must accompany it and exactly how long the clock has left.