fig. 1.0 · the operator
An epoch is a period of time. Yours is about to change.
Epoch exists because brokerage founders deserve one partner who can run the business questions and build the software, instead of a consultant who cannot code and a dev shop that cannot read a P&L.
one operator · both sides
fig. 2.0 · both sides
One partner, both sides.
| 01 | Licensing sequences |
| 02 | Comp plans |
| 03 | P&L discipline |
| 04 | The operational spine |
| 01 | Websites |
| 02 | Custom tools |
| 03 | Integrations |
| 04 | Keystone, operated in house |
The value is not that I do two jobs. It is that nothing falls in the gap between them.
fig. 3.0 · why the geology
Why the rings.
An epoch is a boundary in deep time. Companies have them too: the day you file the MU1, the first funded loan, the month you stop originating and start operating.
The mark on this site is the geologic time scale, drawn as rings. The rings on every sheet are dimensioned by your own attention as you read.
fig. 4.0 · general notes · issue
Details are the deliverable
A comp plan with no version history is a liability. A table with no tabular numerals is a guess. The small things are the actual work.
Show the math
You should be able to see how a number was built, not just what it says. Every figure on this site comes with the arithmetic behind it.
Write it down, version it
A plan that only lives in someone's memory is not a plan. Everything gets a document and a date.
Run what you build
I do not hand off software I would not operate myself. Keystone runs on the same code I would ship to you.
No theater
No stock photos, no manufactured urgency. If something is uncertain, I say so.