Launching today
SonOf
Empty your backlog. Pay only when it ships
37 followers
Empty your backlog. Pay only when it ships
37 followers
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.
DIY UX Test
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.
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.
DIY UX Test
@yuliia_pronΒ Good question. We see three situations where it earns its keep:
You inherited a codebase you can't read. Solo founder, v1 built by a freelancer, an agency, or vibe-coded with Lovable/Bolt β the original developer is gone, the product runs, and nobody knows what's inside. The free audit alone solves half the problem: you finally get a map of what you own.
Your backlog grows faster than your team ships. Founder-led startup, a few in-house devs, and a backlog that's mostly going to die there. SonOf takes the tickets your team will never get to β you approve, it ships, your devs stay on the core.
You can't hire fast enough. Eng teams where the roadmap slips quarter after quarter because every hire takes months. Extra shipping capacity without headcount, and without the agency markup.
The common thread: the value isn't "AI writes code" β it's that unfinished work finally becomes shipped work, and you pay only when it lands in production.
Honestly, the fastest way to see where it helps you is the audit β it's free and it tells you what's broken and what's ready to build before you spend anything.
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.