Connect your repo and PM tools. SonOf audits the codebase, writes and estimates the tickets, and ships the ones you approve. A senior engineer signs every plan and reviews every PR. Billed only when code hits production. Rejected work costs $0.
Hey Product Hunt 👋 Oleksii here, one of three makers.
For 8 years we've run Fulcrum, a dev studio — 100+ products shipped. Every client conversation started with the same two questions: how much will it cost, and when will it be done?
And for years, my honest answer was: it depends.
It depends on a pile of risks. A pile of nuances. Work everything out properly upfront — that's waterfall, and it takes forever. Go with an open check — the risk shifts to the client: they might pay more than they planned. Either way, one thing was constant: clients pay for hours.
Lately there's a third option. Founders try to build with AI themselves. They burn weeks and tokens — and rarely reach real production. Limitations show up. Slop shows up. The money is already spent.
Here's the uncomfortable accounting truth behind all three paths: unfinished work is money that never capitalizes. Half-built features, slipping roadmaps, abandoned prototypes — pure spend, zero asset. Only code in production converts money into value.
And a second problem I kept seeing with non-technical founders: they can't evaluate whether an engineer is good, can't predict budgets, can't see risks. The outsourcing model quietly transfers all of that responsibility onto the person least equipped to carry it.
That's why we built SonOf — for ourselves first. It started as an internal engine to push Fulcrum client work through faster. After ~10 engagements ran on it, we realized we'd built the product. (Yes, it's named after Son of Anton — Gilfoyle's AI in Silicon Valley. We're that kind of team.)
SonOf reads your entire product — repo, tickets, docs — as one context, and does the discovery work that used to take weeks. What you get is something the old model could never give:
→ Full visibility over scope, before you spend anything. Every piece of work becomes a ticket with a fixed price on it — $500 per story point.
→ The timeline in your hands. You approve tickets one by one — what to build, in what order, at what pace.
→ Payment lands where value lands. You're billed only when code reaches production — the moment spend becomes an asset. A senior engineer signs every plan and reviews every PR before merge. Rejected work costs $0.
See what that does to the two problems above? You don't need to judge engineers, budgets, or risks anymore.
So after all these years, my answer finally changed — not because we work differently now, but because the client finally sees what we see.
How much? It's on the ticket, before you say yes.
When? You set the pace — approve, and the engine works around the clock.
Not "it depends."
The audit of your product is free: connect a repo, see your whole map. I'll be in the comments all day.
Oleksii, the honest bit here is that work only counting once it truly ships really lands with me. So many things claim progress long before anything reaches real people, and that framing feels refreshingly grounded.
Charging on outcome instead of effort is rare, and customers notice, most tools bill you for trying and failing. The operational risk is disputes: what counts as shipped, who arbitrates, what happens on a half-done feature. Get that airtight and this is genuinely differentiated.
Sounds interesting! But how can a non-technical client verify that the estimates are adequateand the code quality is high?
Congrats on launch! What are the numbers of how it impacted the projects you'd already delivered?
pay-only-when-it-ships puts the risk on you, not me. that's the rare part. does the senior engineer sign the plan up front, or only review the final pr?
Genuinely impressed that the billing only triggers on code that ships to production. The senior engineer review on every PR gave me confidence to let it touch real tickets instead of just test repos.
Love the name! 😁 What do you see as the main use cases for the product? I'd love to understand where you think it provides the most value.
About SonOf on Product Hunt
“Empty your backlog. Pay only when it ships”
SonOf launched on Product Hunt on July 16th, 2026 and earned 91 upvotes and 14 comments, placing #16 on the daily leaderboard. Connect your repo and PM tools. SonOf audits the codebase, writes and estimates the tickets, and ships the ones you approve. A senior engineer signs every plan and reviews every PR. Billed only when code hits production. Rejected work costs $0.
SonOf was featured in SaaS (43.1k followers), Developer Tools (515.8k followers), Artificial Intelligence (473.7k followers) and Vercel Day (26 followers) on Product Hunt. Together, these topics include over 234.1k products, making this a competitive space to launch in.
Who hunted SonOf?
SonOf was hunted by Oleksii Sekundant. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how SonOf stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Oleksii Sekundant
Hey Product Hunt 👋 Oleksii here, one of three makers.
For 8 years we've run Fulcrum, a dev studio — 100+ products shipped. Every client conversation started with the same two questions: how much will it cost, and when will it be done?
And for years, my honest answer was: it depends.
It depends on a pile of risks. A pile of nuances. Work everything out properly upfront — that's waterfall, and it takes forever. Go with an open check — the risk shifts to the client: they might pay more than they planned. Either way, one thing was constant: clients pay for hours.
Lately there's a third option. Founders try to build with AI themselves. They burn weeks and tokens — and rarely reach real production. Limitations show up. Slop shows up. The money is already spent.
Here's the uncomfortable accounting truth behind all three paths: unfinished work is money that never capitalizes. Half-built features, slipping roadmaps, abandoned prototypes — pure spend, zero asset. Only code in production converts money into value.
And a second problem I kept seeing with non-technical founders: they can't evaluate whether an engineer is good, can't predict budgets, can't see risks. The outsourcing model quietly transfers all of that responsibility onto the person least equipped to carry it.
That's why we built SonOf — for ourselves first. It started as an internal engine to push Fulcrum client work through faster. After ~10 engagements ran on it, we realized we'd built the product. (Yes, it's named after Son of Anton — Gilfoyle's AI in Silicon Valley. We're that kind of team.)
SonOf reads your entire product — repo, tickets, docs — as one context, and does the discovery work that used to take weeks. What you get is something the old model could never give:
→ Full visibility over scope, before you spend anything. Every piece of work becomes a ticket with a fixed price on it — $500 per story point.
→ The timeline in your hands. You approve tickets one by one — what to build, in what order, at what pace.
→ Payment lands where value lands. You're billed only when code reaches production — the moment spend becomes an asset. A senior engineer signs every plan and reviews every PR before merge. Rejected work costs $0.
See what that does to the two problems above? You don't need to judge engineers, budgets, or risks anymore.
So after all these years, my answer finally changed — not because we work differently now, but because the client finally sees what we see.
How much? It's on the ticket, before you say yes.
When? You set the pace — approve, and the engine works around the clock.
Not "it depends."
The audit of your product is free: connect a repo, see your whole map. I'll be in the comments all day.