About
Small on purpose
Caprenna is Sebastian Isaksen and James. Sebastian handles the work in front of clients — what to fix, in what order, and what it's worth. James handles the work behind it — the build, the systems, and the standard they're held to. You'll never be handed to someone junior, because there isn't one.
The name
Caprenna
Three syllables — ca·PREN·na. One word, double N.
Caprenna was a hamlet in the Upper Valdarno in Tuscany, recorded in Emanuele Repetti's Dizionario Geografico Fisico Storico della Toscana in 1833. The settlement is gone. Only the Caprenne torrent still carries the name.
We liked that a place could leave behind something that keeps running.
Operating rules
Four things we put in every engagement
These came out of watching a finished build sit unused for seven weeks while everyone waited politely on an email. They're in the contract now, not the culture.
- 01
One named client-side owner, with authority, agreed in writing before kickoff
Every dependency belongs to a person. Not a department, not "the team."
- 02
Every client-side task gets a date and a name
Never "when you get a chance." That phrase is where engagements go to die.
- 03
We hold the credentials, or we hold a working session
Either we can do the step, or we're on the call while you do it. Never hand off and wait.
- 04
A ten-day stall clock
Anything sitting longer than ten days escalates to a phone call. Not another email.
Standing
Where we are
Caprenna is new. We're a Maryland firm working with professional services firms in the DMV region and beyond, and we'd rather say that plainly than dress it up. What isn't new is the method — it's written down, versioned, and we run it on ourselves first.
What we won't take on yet
No engagements touching protected health information until the compliance question is properly settled. It's the wrong first fight, and we'd rather tell you now than discover it in month two.