wouldit.work

Developer tools

Conductor: a solo QuickBooks Desktop API built for one customer, now at verified $46K MRR

Danny Nemer built a modern API for a legacy accounting system after a broader idea failed. One paying customer shaped the product, GitHub stars and SEO brought the rest, and Stripe-verified revenue keeps climbing.

Product
Conductor
Founder
Danny Nemer
Launched
2022
Model
Usage subscription: $49 per company file per month, Enterprise custom

Published · 2 min read · 3 sources

Key takeaways

  • Started in 2022 for one paying customer (Miter) after a broader data-orchestration idea burned him out.
  • Apr 2026 interview: about $25K MRR, every customer inbound, zero CAC, Ramp as the largest customer.
  • TrustMRR (Stripe-verified, 4 Nov 2026): $46,152 MRR, 307 active subscriptions, $508,110 all-time revenue.

What it is

Conductor is a typed API and SDK set (Python, Node.js/TypeScript, REST and MCP) for QuickBooks Desktop and Enterprise, an accounting system that still runs many businesses but has no modern web API (Conductor). It "completely abstracts away the fragility and quirks of QuickBooks Desktop, the Web Connector, qbXML, SOAP" (Conductor). Pricing is $49 per company file per month in production, with a free trial (TrustMRR).

Timeline

  • 2022: Danny Nemer starts Conductor after working as founding engineer at Afresh (IndieNiche interview); TrustMRR lists it as founded in July 2022 (TrustMRR).
  • First customer: a founder friend introduces him to Miter, which needs a QuickBooks Desktop integration; he builds an API and an npm package with "no landing page, dashboard, or sign-up flow" for it (IndieNiche).
  • About 1.5 years in: he adds a sign-up page; before that, users filled out a Typeform and he created accounts by hand (IndieNiche).
  • Apr 2026: "We're at about $25K MRR right now," growing around $1.5K in new MRR a month (IndieNiche).
  • 4 Nov 2026: $46,152 MRR, 307 active subscriptions and $508,110 all-time revenue, verified with Stripe (TrustMRR).

Why it worked

  • A real customer before a product. His first, broader attempt failed because he "had no committed user and no tight feedback loop"; the paying customer fixed that (IndieNiche).
  • A small but deep niche. He resisted the niche at first, but "the niche became Conductor" (IndieNiche).
  • GitHub as a search engine. He asked friends and customers to star the Node.js SDK repo so developers searching GitHub for QuickBooks Desktop would find it; later SEO joined in, and "every customer came inbound, and CAC stayed at zero" (IndieNiche).
  • Trust through competence. Warm intro, phone call, build the exact feature, prove it works. That got him Ramp as his largest customer (IndieNiche).

What to learn

  1. Ugly legacy systems are good markets: buyers go looking for help and rarely want to build it themselves.
  2. Build the narrowest thing a paying customer needs in production, then let their requests set the roadmap.
  3. Developers search GitHub. A well-starred SDK repo can be a discovery channel when your website does not rank yet.

Risks and what didn't work

  • Heavy dependence on one platform: if Intuit changes or retires QuickBooks Desktop, the core market shrinks.
  • The founder's first idea, a broad data orchestrator, failed and he "burned out without a real user" (IndieNiche).
  • Early growth was slow because the website "ranked poorly in Google for a long time" (IndieNiche).
  • The founder's TrustMRR note says it "completely runs itself" and has "virtually no churn"; those are his claims, while the revenue figures are Stripe-verified (TrustMRR).

FAQ

Short answers drawn from the sections above.

What is Conductor?

Conductor is a typed API and SDK set (Python, Node.js/TypeScript, REST and MCP) for QuickBooks Desktop and Enterprise, an accounting system that still runs many businesses but has no modern web API (Conductor). It "completely abstracts away the fragility and quirks of QuickBooks Desktop, the Web Connector, qbXML, SOAP" (Conductor). Pricing is $49 per company file per month in production, with a free trial (TrustMRR).

Why did Conductor work?

  • A real customer before a product. His first, broader attempt failed because he "had no committed user and no tight feedback loop"; the paying customer fixed that (IndieNiche).
  • A small but deep niche. He resisted the niche at first, but "the niche became Conductor" (IndieNiche).
  • GitHub as a search engine. He asked friends and customers to star the Node.js SDK repo so developers searching GitHub for QuickBooks Desktop would find it; later SEO joined in, and "every customer came inbound, and CAC stayed at zero" (IndieNiche).
  • Trust through competence. Warm intro, phone call, build the exact feature, prove it works. That got him Ramp as his largest customer (IndieNiche).

What can indie builders learn from Conductor?

  1. Ugly legacy systems are good markets: buyers go looking for help and rarely want to build it themselves.
  2. Build the narrowest thing a paying customer needs in production, then let their requests set the roadmap.
  3. Developers search GitHub. A well-starred SDK repo can be a discovery channel when your website does not rank yet.

What didn't work for Conductor, and what are the risks?

  • Heavy dependence on one platform: if Intuit changes or retires QuickBooks Desktop, the core market shrinks.
  • The founder's first idea, a broad data orchestrator, failed and he "burned out without a real user" (IndieNiche).
  • Early growth was slow because the website "ranked poorly in Google for a long time" (IndieNiche).
  • The founder's TrustMRR note says it "completely runs itself" and has "virtually no churn"; those are his claims, while the revenue figures are Stripe-verified (TrustMRR).

Sources

Every link cited above, in order of first use.

  1. 1.Conductor (conductor.is)
  2. 2.TrustMRR (trustmrr.com)
  3. 3.IndieNiche interview (indieniche.substack.com)

Related case studies

More in Developer tools →