Loading page…
White-label accounting and tax software embedded inside small-business platforms, monetized as those platforms add more customers.
lifetime profitable after recovering more than $5M burned · multi-million-dollar annual income-tax bill stated · 21 employees
The sale is not to the small business using the ledger; it is to the platform that already owns the relationship and wants accounting to feel native.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Raj Bhaskar and his brother Anu started Hurdler in Washington, D.C., at the end of 2011 with a long view and their own money. The product is embedded accounting: QuickBooks- and TurboTax-like functionality that another small-business software company can put inside its own product under its own brand. Hurdler first sold directly to small businesses because it needed a live showcase, then spent roughly six years converting toward the original embedded vision. The proof is unusually concrete. Hurdler has served over 1.3 million small businesses, has 21 employees, and became lifetime profitable after recovering more than $5 million lost during the build period. Raj says the company now pays multi-million dollars in income tax each year, although he does not disclose exact revenue. Clients include ZenBusiness Money and Collective Accounting; some early clients grew from four figures of monthly recurring revenue to six figures for Hurdler as their own customer bases expanded. The company gets roughly 40% of prospects through organic search, 40% through referrals, and 30% through outbound outreach. Its durable advantage is not a flashy feature: it is the accumulated accounting, tax, migration, integration and service knowledge required to become a financial system of record inside another platform.
The first meaningful embedded customers came after years of building a direct-to-SMB product as a working API showcase. Raj says Hurdler waited five to six years for its first API lead.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Founder interview on Practical Founders. Raj Bhaskar states the operating and traction figures about Hurdler, so the grade is Founder-Reported rather than independently verified. The transcript states over 1.3 million small businesses served, 21 employees, more than $5 million burned before lifetime profitability, multi-million-dollar annual income tax, 40% organic leads, 40% referrals, 30% outbound, a few hundred thousand monthly active users on the former free direct product, and clients growing from four-figure to six-figure monthly recurring revenue for Hurdler. Exact revenue, pricing, margins, customer count, investor amount and audit evidence are not disclosed. The $3 million figure refers to founder capital put in at the start, not revenue. No exchange-rate conversion is needed because the disclosed figures are in U.S. dollars or percentages.
Hurdler's first revenue arrived in an indirect way. The founders built an API, then built a direct small-business application around it because no API lead appeared.
The flywheel began when Hurdler's customers started growing. Raj says some clients that began at four figures of monthly recurring revenue for Hurdler later reached six figures as those clients put more of their own customers onto the product.
The no-feedback stretch lasted far longer than a normal startup launch. Hurdler took five to six years to get its first API lead, and the founders put in the first $3 million themselves.
Hurdler is a financial operating layer that other software companies can embed and white-label. It covers invoicing, payments, expense tracking, financial statements and real-time income-tax calculations for all 50 states and Washington, D.C.; the company also supports Canadian provinces. The product serves owner-operators with a simpler view of profitability and cash flow while giving bookkeepers and accountants a separate workflow for ledgers, journal entries and reconciliations. The important product boundary is strategic. Hurdler does not try to become the payroll or payments provider; it integrates with providers such as Stripe and embedded payroll vendors, then unifies the results in the general ledger. That neutrality lets the platform customer keep its own revenue opportunities. ZenBusiness Money is one example named in the interview, and Collective Accounting white-labels Hurdler as the operating system for its virtual bookkeeping service. Our read: the defensibility is in the long tail of correctness — tax rules, data imports, support, integrations and workflows — not in the first dashboard a developer can copy.
Exact revenue and pricing are private. What Raj discloses is that Hurdler has served over 1.3 million small businesses, is lifetime profitable after recovering more than $5 million of losses, pays multi-million-dollar income tax annually and has clients whose Hurdler MRR grew from four figures to six figures. The likely commercial engine is usage or customer volume inside each platform, because he says client growth expands Hurdler revenue. Our read: the cleanest version of this model combines an implementation or onboarding charge with recurring usage revenue and optional services engineering. The recurring line compounds as a platform adds customers; the services layer protects activation and reduces churn. Hurdler's decision to remain neutral on payroll and payments also matters economically: partners can monetize those products, so Hurdler is easier to approve as a revenue-enabling layer. The company invested heavily before the model was obvious, including the founders' first $3 million and a later minority VC investment. That is not a low-cost micro-SaaS; it is a long-duration infrastructure business whose payback depends on becoming embedded in a customer's core workflow.
The transcript gives no exact software stack, gross margin or operating-cost breakdown. It does give the shape of the cost base. Hurdler maintains accounting logic, tax calculations for every U.S. state and D.C., Canadian rules, data imports from QuickBooks and Xero, payment and payroll integrations, customer support and implementation assistance. The company had 21 employees at the time of the interview, including roughly 16 developers. The founders' main productivity advantage was accumulated domain knowledge: the first four people came from the prior venture and the engineers already understood accounting. That shortened the path to feature parity with much larger products. Our read: a new entrant should not begin with a general ledger for every industry. Start with one vertical platform and a small, auditable subset of workflows, then charge for the integration and learning. The largest costs will be compliance, correctness and customer-specific implementation, not hosting. A high retention rate can make those costs rational; a low attach rate turns them into bespoke consulting. Treat implementation time as a product metric from the first pilot.
Copy the distribution insight: sell infrastructure to the software company that already has the end-user relationship. Copy the free or low-friction showcase only if it produces a measurable proof point, and copy the separation between owner-operator UX and accountant UX. The second API customer was more informative than the first because it suggested repeatability. Change the scope. Hurdler spent years building a broad accounting and tax surface, and the founders supplied $3 million before the category matured. A new founder should pick one vertical, one high-value workflow and one integration path. Charge for the pilot, instrument activation and ask the platform to show the feature in its pricing or onboarding. Keep the neutral-partner stance when the platform makes more money from payments, payroll or services than it would by replacing them. Our read: the copyable business is not “build QuickBooks”; it is “remove one expensive financial hand-off from a platform that already has distribution.”
The biggest risk is correctness. Accounting, tax and payment software can create legal, financial and reputational damage when a calculation or migration is wrong. The product also faces integration risk: a platform may postpone the project because it has too many priorities, even when the need is real. Hurdler's founder says the core objection is often when to prioritize embedding, not whether it is valuable. There is concentration risk on the platform side. A few large customers can create substantial usage, but they can also change strategy, build internally or stop growing. Regulatory maintenance is another permanent cost, especially when supporting state tax rules and financial records. The long sales cycle means a small company can spend months in technical and commercial review before seeing revenue. Our read: a focused entrant should limit supported jurisdictions, define contractual data responsibilities and price for implementation. The business works when the feature becomes hard to remove and the partner's revenue grows with usage; it fails when it becomes an underpriced custom integration with no recurring expansion.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click