Formation
We assemble the party before we assemble the deal. Most structures fail because they were drawn around incentives that had not yet been said out loud. We say them first, and we write them down where both sides can see them.
We form partnerships and hold them past the point at which most parties stop holding.
ScrollWe assemble the party before we assemble the deal. Most structures fail because they were drawn around incentives that had not yet been said out loud. We say them first, and we write them down where both sides can see them.
A partnership is an obligation that has to be maintained. We hold the maintenance work — reporting, arbitration, the slow correction of drift — for as long as the relationship remains worth holding.
Software is where an agreement becomes observable. Our engineering practice builds the instruments a partnership needs in order to see itself: ledgers, terminals, controls, and the reporting that sits under all three.
Every arrangement contains more capacity than its parties use. We locate it, price it, and route it back into the position rather than out of it.
We read the counterparty before we read the opportunity. Nothing is proposed in the first six weeks.
Terms are drafted against stated incentives, not against precedent. Where the two disagree, precedent loses.
The agreement is given a surface. Positions, obligations, and thresholds become things both parties can look at on the same screen.
We run inside the partnership rather than alongside it. The work is ordinary and continuous.
Every arrangement is repriced on a fixed cadence. Continuation is a decision, taken deliberately, and it is taken often.
Value does not accrue to the party with the best terms. It accrues to the party still present when the terms stop mattering.
Most arrangements are priced at formation and never repriced. We take the opposite view: a partnership is an instrument whose value is discovered slowly, in the ordinary work of keeping it intact. That work is the practice.