Punch Raises $2M for Construction Intelligence Platform

Some of Punch's customers have bought a stake in the company building their next operating tool. For founder and CEO Taylor Sandusky, that puts people who know the inconvenience of construction paperwork on both sides of the product conversation.

Punch, an Atlanta construction software company founded in 2025, announced $2M in financing on October 15, 2026. Returning investor Gutter Capital is backing the business alongside unnamed customers and technology angels. The money will support engineering and customer teams, platform development and wider contractor adoption; the announcement does not identify a round type or valuation.

Punch turns spoken jobsite updates, photographs and emails into reports, purchasing documents and follow-up using a contractor's own rules. That makes its growth story about an awkward piece of construction management: getting the knowledge held by experienced people into a form that colleagues and software can act on while the job is still moving.

The financing follows contractors into the product

Sandusky spent years managing construction projects before founding Punch. The company's history and founding details describe purchasing, invoice checking and administrative work as the starting problems. Contractors helped shape the platform around those tasks, and several customers subsequently invested, according to the issuer's funding release.

Gutter Capital's Elbow Grease accelerator identifies Sandusky as Punch's CEO. Dan Teran, Gutter Capital's co-founder and managing partner, links the investment to Sandusky's experience in construction and the opportunity to give leadership a clearer view of individual projects. The returning relationship matters as context, although the current disclosure leaves earlier funding amounts and cumulative capital unspecified.

Customer investment adds an interesting feedback channel. A contractor using the product encounters the supplier mismatch, missing approval or late report that a demonstration can glide past. That relationship can give the development team useful pressure to solve ordinary problems. The announcement supplies no breakdown of investor allocations or customer identities, so the ownership story stops there rather than turning every logo into a cap-table entry.

The engineering and customer-team expansion also belongs together. A product that relies on each contractor's processes needs help learning those processes. Some of the work funded by the $2M will sit in conversations about how a company actually buys and manages work.

A field message needs the office's context

Punch describes its operating loop as an update arriving through mobile, email or the web portal, followed by work carried out against company and project playbooks. Those playbooks hold information such as cost codes, supplier choices, pricing and approval requirements. A request for material can therefore arrive with the context needed to prepare a purchase order.

That context has a practical owner. The contractor decides whose approval matters and which rules govern the job; Punch says orders requiring sign-off wait for it. The product's explanation keeps the purchasing conversation visible to the user, including supplier communications and exceptions. Giving software a useful next step requires deciding where its authority ends.

Procurement controls bring that boundary into the buying process through approved materials, suppliers and pricing. Invoice and pay-application review extends it into checking what a supplier or subcontractor asks to be paid. The business value runs across the transaction, from deciding what should be ordered to checking the bill that follows.

Punch works alongside estimating and accounting systems, placing it near a market also drawing capital into construction accounting AI and construction operating software. For buyers, the resulting question is how reliably information travels between the jobsite and those existing records. That is also where implementation becomes consequential: a polished voice interaction is useful only when the contractor's own purchasing and project context travels with it.

Customer evidence comes in different forms

The issuer's Business Wire release names Dustin Gibbs, general superintendent at Piedmont Drywall, who reports reducing daily-report preparation from 30 minutes to 3. Across reports, material orders and payroll, Gibbs estimates saving about 2.5 hours a day. These are attributed customer results, rather than an independently audited average across Punch deployments.

A separate company-published walkthrough shows why the output matters beyond the minutes saved. A superintendent's question about whether work belonged within the contractor's scope became an assigned task for the project manager. Administrative effort buys something more useful when a question reaches a person who can resolve it.

Another drywall contractor's business case models $178K in expected annual savings across material mistakes, labor overbillings, earlier problem detection and a retired reporting application. That figure describes a prospective calculation. A buyer evaluating it would still need to compare the assumptions with actual purchasing patterns, staffing and errors at its own company.

The distinction between a customer's time report and a projected financial model gives operators a better starting point than a blended productivity headline. Each asks a different question: what changed for a superintendent already using Punch, and what might change economically across a contractor's year.

Customer implementation becomes part of the expansion

Punch's pricing approach uses a scoped value case rather than fixed published tiers. The company targets a return of 5-10 times the software cost in its proposals. That is a commercial target to evaluate against a contractor's own operation, not an established return for every customer.

For construction leaders, this puts the buying discussion close to the way a job makes or loses money. The company needs to explain its approval chains, recurring mistakes and administrative workload. Punch then has to translate that explanation into working behavior across reports, purchases and invoice checks. Product development and customer support meet inside that translation.

The same work has a training consequence. Supplier preferences and project procedures often belong to experienced employees who know when an exception deserves attention. Making those rules available to newer colleagues changes how that experience travels through the company. Punch's expansion will take its team into more of those conversations, where the next request from the field arrives before anyone has had time to write the manual.