The thing your fund does differently should not be a feature request.
Every fund has one process it will not give up — the scoring rubric that actually works, the LP letter the anchor expects, the entity structure the auditor signed off on. Most platforms hand that to an implementation partner and a six-month statement of work. We put the people who build the product on it, and what they build for you is not a bolt-on: it is configuration on the same product every other fund runs, or it becomes the product.
Scope, migrate, build, ship.
Quoted against a scope you approve first. Each step ends with something you can check against your own numbers.
- Scope 01
A week inside your actual process.
Not a requirements document. The spreadsheet you really use, the memo template, the report the LPs actually read. We map it before anything is configured, and we tell you which parts the product already does.
- Migrate 02
Ten years of history, carried over.
Cap tables, capital accounts, closed deals, the folder of signed documents. Extracted, reconciled against your own numbers, and checked by a person before anyone signs off on it.
- Build 03
Your rubric. Your bands. Your letter.
Scoring factors, report templates, entity structures, waterfall terms — configured to your fund, on the standard product. Nothing forked, so an upgrade never breaks what we built for you.
- Ship 04
When it is not configuration, it is roadmap.
The requirement no setting covers goes to the same engineers who ship the product, with a stated date. You are working alongside the team that owns the code, not a partner who files a ticket with them.
Configuration, or it becomes the product.
Every request ends in one of two places. If a setting covers it, it is configuration on the standard product — the same one every other fund runs, so an upgrade never breaks it. If no setting covers it, it goes to the engineers who ship the product, on the roadmap with a stated date, and the fix ships to every fund.
There is no third place. No fork of the code for one customer, and no partner firm filing a ticket on your behalf.
What it does not do: gate your start. You can be live on your own in a day, on the free tier or on Solo, and never speak to us. Services exist for the fund that wants hands on the wheel — a complicated migration, a multi-entity structure, a process worth preserving exactly — not as a tax every customer pays before the software works. Scoped and quoted per engagement.
The people doing this build the product.
Every engagement is staffed by our own professional-services team, and they sit with the engineers who ship the software rather than at a partner firm. That matters at exactly one moment: the week a scoping session turns up something your old system did that no setting in ours covers — a fee structure, a side letter, a waterfall term. At most platforms that becomes a workaround you maintain forever. Here it goes to the roadmap with a stated date, and the fix ships to every fund, including yours.
None of it is mandatory. A fund with clean history and no legacy vehicle can do the whole thing self-serve and never speak to us; services are scoped and quoted per engagement, only when you want the hands on the wheel.
Scope your own engagement.
Tell us the process you will not give up. We will come back with what is already configuration and what becomes roadmap.