Five products, five bills, and one person carrying data between them.
That’s the problem Crewbound was built for. Not because the existing tools are bad. Most of them are good at the one thing they do. It’s that a home-services shop’s actual work doesn’t come apart along those lines.
The thing nobody owns
A job at an HVAC shop produces a customer, an appointment, a set of photos, some hours worked, a part list, an invoice, a payment, a review, and a line on somebody’s paycheck. In practice those get spread across a photo app, a field-service platform, a messaging product, a time clock, and an accounting package.
Every one of those companies owns its box well. Not one of them owns the link, and the link is where all the cost is. It’s the re-typing, the reconciling, the invoice that goes out missing the photos, the tech whose Tuesday hours got attributed to the wrong job, the review request nobody sent because the job was marked done in a system that has never heard of the customer’s phone number.
Crewbound is built the other way round: one record first, and the five jobs as views of it. That’s not a feature comparison, it’s a data model, which is why a neighboring product can’t copy it without rebuilding itself.
Where we actually are
Pre-launch. There are no paying shops yet, no case studies, no usage statistics, and nothing on this website is a testimonial. We don’t have any, and inventing them would be the first thing we’d have to lie about.
What does exist is most of the operating system: the office portal, the field app, the shared inbox with real texting and voice on your own number, estimates and invoices and payments, the price book, the time clock and timesheets, reviews, and reports. QuickBooks accounting runs against a stand-in so the flow is complete end to end; the live Intuit sync and QuickBooks Payroll are the next two things we build.
We’re looking for a small number of founding shops, 4 to 10 techs, willing to run real work on something young and tell us exactly where it hurts, in exchange for a permanent discount and a direct line to the people building it. That is a real trade with a real downside, and we’d rather say so than dress it up as an exclusive beta.
Who builds it
Crewbound is a product of Penderra LLC. It’s a small operation, and we haven’t put a fake leadership page on this site. If you want to know who you’d be working with, book a demo. You’ll be talking to them.
Five principles, and they settle arguments.
These aren’t values on a wall. They’re the rules we use when two reasonable designs disagree, and every one of them has killed a feature we wanted.
One record, five tools
Every feature has to strengthen the link between a job, a customer, a photo, an hour, and a dollar. A feature that creates a second, unlinked record is working against the only thing that makes this worth building.
The owner's attention is the scarcest thing here
This gets used in gaps: between calls, at a counter, in a cab. So we design for short, interrupted, re-entered sessions: surface what needs a decision now, make state obvious when you come back, and never require an uninterrupted hour.
Never leak across companies
Multi-tenant isolation is a promise, not just a security control. Every table carries a company id and the database refuses rows that aren't yours. It constrains every query and every surface we build, permanently.
Say the true state
Activation waits, stand-in integrations, failed syncs, and unsent documents show up as what they are. A convincing lie about system state costs more trust than an honest delay does, which is why this website lists what we haven't built.
Speak the trade's language
Telecom, accounting, and platform vocabulary stay on our side of the wall. You will never be asked to understand what a 10DLC campaign is in order to text a customer back.
Come be difficult about it.
The most useful conversation we can have right now is with an owner who tells us what we got wrong. Book thirty minutes and bring your real week.