Choosing a 409A Platform When You're Building Your Own Product
A lot of custom software and product engineering firms start as billable-hours shops and only later carve out a product line they actually own. That shift changes what a 409A valuation is even measuring: appraisers stop looking only at contract backlog and start asking what the owned IP is worth on its own. Getting Carta or Shareworks in place before that transition makes the eventual valuation cleaner.
This matters most for the founder who's already granting equity to a handful of senior engineers to keep them from jumping to a competitor, and who is about to make the services-to-product shift without having thought through what it does to the cap table.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Step one: what are you actually valuing?
If the business is still pure services, with revenue by client, margin by engagement, and utilization by engineer, a 409A appraiser will often lean on an income approach built from that contract history. Once a portion of the company is a product with its own customers, licensing revenue, or recurring subscriptions, the valuation needs to split the enterprise value between the services book and the product line, which is a harder report to write and a good reason to get your cap table platform sorted before that split shows up on the balance sheet.
Write down, in plain language, what percentage of last quarter's revenue came from services versus the product line, and update that split every quarter. It's a simple habit, but it's exactly the input an appraiser will ask for first, and having it ready saves a round of back-and-forth.
Step two: decide how concentrated your equity pool is
Development shops often grant equity to a small number of senior engineers and architects rather than broadly across the team, since retaining two or three people who understand the whole codebase matters more than a wide grant program. Carta handles a small, option-heavy pool with minimal overhead, which fits this pattern well. Shareworks' strength shows up once that pool widens, more grant types, more employees, more jurisdictions, so a five-person option pool rarely needs what Shareworks is built for yet.
That said, concentration cuts both ways in a valuation. An appraiser pricing a company where two engineers hold the entire architectural knowledge of the codebase will typically apply a larger key-person discount than one pricing a company with a broader, more redundant engineering bench. Document a real succession or knowledge-transfer plan for your most critical engineers; it's one of the few things a founder can do to directly influence that discount.
Step three: check whether client contracts create IP ambiguity
Work-for-hire and IP assignment terms in your client contracts directly affect what an appraiser can count as company-owned intellectual property. A shop that has been quietly building reusable frameworks or internal tools across client engagements should have counsel confirm which of those assets the company actually owns before a valuation tries to price them. This is a legal question, not a platform question, but it changes the inputs either vendor's analyst will need from you.
Step four: which platform matches your growth plan?
If you plan to stay a project-based shop indefinitely, Carta's lighter administrative footprint is usually the better fit. If you're deliberately building toward a product spinout, a separate cap table for that entity, or outside investment specifically for the product line, evaluate Shareworks now for the entity that will eventually carry the more complex equity plan, so you're not migrating platforms in the same quarter you're negotiating a new round.
A middle path some shops take is standing up a genuinely separate legal entity for the product line from day one, with its own cap table on whichever platform fits its trajectory, while the services business keeps running on lighter tooling. That separation also makes the eventual valuation split cleaner, since the appraiser isn't trying to untangle product revenue from services revenue inside a single entity's books.
Step five: set your refresh cadence around delivery cycles, not the calendar
Development shops often see revenue swing sharply between a heavy delivery quarter and a lighter one between contracts. If your last 409A was priced during an unusually strong quarter and the following quarter looks materially different, don't wait for the twelve-month mark to reconsider: a material change in revenue trajectory can be a trigger for a fresh valuation, independent of the calendar.
A simple habit helps here: whoever owns finance should compare actual quarterly revenue against the assumptions baked into the last valuation every quarter, not just at renewal time. If the gap grows large enough that an outside appraiser would clearly land on a different number today, that's the signal to move early rather than waiting out the clock.
Run through the five steps in sequence:
- Decide whether an appraiser will value you as a pure services firm or as a business with an owned product line.
- Check how concentrated your equity pool is among senior engineers and architects.
- Have counsel confirm which reusable frameworks or tools you own under your client contracts' work-for-hire and IP assignment terms.
- Match the platform to your plan: stay project-based, or build toward a product spinout or outside investment.
- Set your refresh cadence around delivery cycles, and reconsider early if revenue shifts materially.
What Good Looks Like
A software development company that carries both a services book and owned IP can point to which parts of its valuation come from each, and keeps its equity platform sized to its actual grant volume rather than to where it hopes to be in three years.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Ensure accurate 1099 and year-end tax compliance alongside employee and contractor equity vesting schedules.
Streamline corporate spend management, venture banking, and automated audit trails for cap table expenses.
Automate corporate expense controls, accounting sync, and financial close documentation ahead of valuation audits.
Frequently Asked Questions
Should a services company even bother with a 409A if it isn't chasing venture funding?
Yes, if it grants stock options to anyone. Section 409A applies to private companies of any funding profile, not only venture-backed ones, so a bootstrapped dev shop granting options generally needs a defensible valuation to support a strike price at fair market value.
How does splitting off a product line affect an existing 409A?
It usually triggers a new one. Once a meaningful share of value sits in owned IP rather than service contracts, the comparable companies and valuation method an appraiser would use both change, so the prior report no longer reflects the business accurately.
Can a five-person option pool justify the cost of a full platform migration?
Usually not yet. A small, simple pool is often cheaper to manage with a lighter tool until grant volume, instrument variety, or headcount grows enough to justify the administrative overhead of a heavier platform.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Setting Up Equity Software Before Your First Priced Round
A step-by-step look at when a custom software and product engineering shop needs Pulley or Carta for option grants, fair market value and vesting records.
Audit Tool Pitfalls for Custom Software Development Firms
The specific mistakes custom software and product engineering firms make choosing between FloQast and AuditBoard for WIP, capitalized costs and SOX readiness.
BILL vs Tipalti for Custom Software and Product Engineering Shops
Development shops that lean on outsourced or overseas engineers face a different AP problem than in-house teams. Here's how BILL and Tipalti compare for that.
Software Development Firms: Cube vs Mosaic for Project Margin
How Cube and Mosaic differ for a custom software shop: tracking fixed-bid margin, capitalized development hours, and utilization by sprint.
Ramp vs Brex for Custom Software Shops Billing by Project
How Ramp and Brex compare for custom software and product engineering shops that need to track spend against fixed-bid and time-and-materials contracts.
Pipe vs Capchase for Custom Software Shops: What Qualifies
Custom software firms mix project billing with recurring contracts. See which revenue Pipe and Capchase can finance and where venture debt fits better.