AdHocBucket wants to replace post-hoc billing guilt with a prepaid time wallet. Here's the honest case for and against it.
There's a specific kind of consultant pain that never makes it into startup pitch decks. A client sends a Slack message at 4pm: "Quick question — should take you 10 minutes." The consultant answers. It takes 25 minutes. They close the tab and never bill it because raising an invoice for $87.50 feels socially weird and administratively annoying. This happens three, four, five times a month. That's $400–600 silently evaporating.
The r/consulting threads on this are not subtle. People are frustrated in the specific, detailed way that signals real pain rather than venting. G2 reviews of Harvest call out "endless back-and-forth invoicing for small tasks." Dubsado users on Reddit explicitly say retainer tracking is manual and error-prone. The problem has a shape: it lives after the work is done, not before or during.
AdHocBucket is an embeddable widget that tries to solve exactly this. Clients buy prepaid hour bundles (2, 5, or 10 hours) directly from the consultant's website. They submit async requests through the portal. Time gets deducted automatically. When the balance runs low, the client gets an alert and a one-click top-up link. The consultant gets a new-request notification. Nobody sends an awkward invoice for 0.4 hours of work.
The mechanic is clean. The aha moment the product is chasing — a consultant receiving a client top-up notification without having sent an invoice — is genuinely satisfying to think about.
Here's the thing I keep coming back to: the product's core bet isn't on technology. It's on behavior change. The consultant has to convince their client to pre-pay for work that hasn't happened yet, through a new portal they've never seen, instead of the existing arrangement they're comfortable with.
AdHocBucket has zero involvement in that conversation. If a consultant can't make that pitch land, the wallet sits empty, the consultant churns, and no amount of UX polish fixes anything. The product's survival metric — funded client wallets, not consultant signups — depends entirely on a sales conversation the product can't control or even observe until after it succeeds or fails.
The fatal flaw analysis estimates that if 50%+ of consultants fail to activate a single client wallet, churn becomes structural. That's a real risk. Client wallet activation is the only metric that actually matters, and it's the hardest one to move from a product level.
There's a secondary constraint worth being honest about: a meaningful slice of solo consultants don't have websites. They run everything through LinkedIn, email, and Calendly. An embeddable widget requires something to embed it in. The real addressable market is smaller than the headline TAM of 300K once you filter for consultants with owned web presence and enough recurring client volume to make prepaid bundles sensible. My guess is you're looking at something closer to 60–80K genuinely addressable users, which changes the ARR math considerably.
Stripe's customer balance API already supports prepaid credit top-ups. Combined with Stripe's embeddable payment links, a technically fluent consultant could replicate roughly 60% of the v1 MVP in a few hours with no monthly fee. This isn't theoretical — it's a real substitution risk, and it means AdHocBucket's survival depends on the workflow layer being dramatically better than duct-taped Stripe, not just more convenient.
That's actually achievable! The async request queue, the per-client balance ledger, the change-order conversion flow, the bundle-size recommendation engine — none of that is easy to replicate ad hoc with Stripe primitives. But it takes longer to build than the payments layer, which means there's a window where the product is most vulnerable to DIY substitution.
What I find interesting about AdHocBucket is that it's specifically not a time tracker or a project management tool. It does one weird specific thing: it converts ad-hoc work into pre-paid async requests. That narrowness is a design choice, and I think it's the right one.
Harvest, Toggl, FreshBooks, HoneyBook, Dubsado — all of them require the consultant to do the administrative lifting after the fact. None of them have a client-facing prepaid wallet mechanic. That gap is real. No YC company has touched it. That's actually a meaningful signal in a space where YC has funded multiple takes on freelancer tooling.
The bilateral switching costs argument is also underrated. Once a client has pre-funded money sitting in the system, they're not going to ask to switch to net-30 invoicing. That friction works in the product's favor. The request history and deduction ledger becomes a compliance audit trail that consultants start referencing at contract renewals. Lock-in through utility, not artificial barriers.
If the AI layer gets built properly — bundle-size recommendations based on historical request patterns per client type — that's a genuine data moat that no generic billing tool can replicate without the same network of consulting workflows. It takes time to accumulate, but it's directionally real.
The validation test here is worth taking seriously: build a Typeform, manually wire it to a Stripe Payment Link, use Airtable as the dashboard, and DM 20 consultants from r/consulting with a Loom walkthrough. Run it manually for free for two weeks for the first five who say yes. If you can't find three people willing to pay $29/month before writing a line of code, stop.
That test is cheap. The 4–6 week solo dev timeline for a shippable MVP using Next.js, Supabase, Stripe webhooks, and Resend is realistic. The $29/month Solo tier with a 14-day free trial is a reasonable ask. At 18 paying customers, you're covering infrastructure. At 100, you're at $2,900 MRR on 88% margins with a product that took six weeks to build.
The ceiling on this business is probably a profitable $1–3M ARR lifestyle SaaS, not a venture-scale outcome. The market isn't large enough to attract serious investment, and the moat erodes quickly if HoneyBook or Stripe decides to ship a wallet feature as a minor product increment. That's not a reason not to build it — for an indie hacker or solo founder, a profitable SaaS at $1M ARR is a genuinely good outcome. But it changes who should pursue this and what success looks like.
If you're a consultant yourself who has personally eaten $300 in unbilled ad-hoc work in the last 90 days, you're the exact right person to build this. You understand the pain, you have the network for early distribution, and you can validate the client activation problem with your own clients first. That unfair advantage matters more here than any technical edge.