Private systems,
built once, owned
by you.
I spent five years inside a family office building the systems its staff used every day. I now do that work independently, for a small number of offices at a time.
How I Work
Family offices run on a particular kind of complexity. The work is bespoke by nature, the tolerance for error is low, and most of what matters never appears in an off-the-shelf product. The usual answer is a spreadsheet that one person understands and everyone else is afraid of.
I build the alternative: private, purpose-made systems for the things your office actually does — a travel and itinerary portal for the principal and their family, an internal reporting layer, a staff-facing operations tool, an intake process that stops living in someone's inbox. Built properly, documented plainly, and handed over.
You work directly with me. There is no account manager, no offshore team, and no junior learning on your engagement.
Your Infrastructure
Everything is built on your accounts and your hosting. Nothing depends on a platform I control, and there is no seat fee waiting for you later.
You Own It Outright
Every system, script, and configuration is yours. If you took it to another developer tomorrow, the documentation would let them pick it up.
Discretion Assumed
No case studies, no logos, no screenshots, no naming you as a client. That is the default and it does not require asking.
Remote, Deliberately
All work is done remotely against systems you grant access to, with access scoped to the engagement and revoked at the end of it.
What It Looks Like
Scoped privately in conversation. For planning purposes, this is the shape most engagements take.
A typical bespoke build — discovery, design, implementation, documentation and handover — delivered across roughly three to five months, with milestone billing.
Ongoing, an optional service retainer keeps the system current as the tools around it change: monitoring, small enhancements, priority response and a quarterly review. Most offices choose this rather than letting a system quietly age.
Smaller pieces of work and short advisory engagements are scoped individually. I will tell you honestly if what you need is smaller than this.
-
Conversation
A private call about what your office is trying to do and whether I am the right person for it.
-
Discovery
I learn the actual workflow from the people who run it, and write it back to you in your own language to confirm I have it right.
-
Build
Fixed scope agreed in writing, milestone billing, and a working version in front of you early rather than at the end.
-
Handover
Documentation, a working session with your staff, and a defined support window. The service retainer starts only if you want it.
Start a Conversation
Two fields. I reply personally, usually within a business day.
Or write directly: erika@stroikops.com