The team
The whole company is on this page.
Two people. No account manager, no bench, and nobody between you and the person writing your software — and both names are on every release. Here is exactly what each of us owns.
- The whole company
- Two people
- Obie, on production systems
- Twelve years
- Building on frontier models
- Eighteen months
Obie
Founder · Lead Full-Stack Engineer
Twelve years designing, building and scaling production systems across enterprise and SaaS, and eighteen months building with frontier AI models every day. Writes the architecture, reads everything the AI produces, and signs off on what ships.
- TypeScript
- Python
- PHP
- React
- Next.js
- Vue.js
- Angular
- Node.js
- Django
- PostgreSQL
- MySQL
- MongoDB
- Supabase
- Docker
- Kubernetes
- Helm
- AWS
- Google Cloud
Owns
Architecture and the data model
Boundaries, schemas, and the decisions traffic makes permanent.
Security and access
Authentication, authorization, and what data any given role is allowed to touch.
What ships
Every release is reviewed and signed off before it leaves. His name is on it.
You will hear from him when
A technical trade-off needs your call — and at every release, whether or not there is anything to decide.
Priscilla
Partner · Strategic Operations
Runs engagements from the first conversation through release. Keeps the scope written down, the dates honest, and the work moving between planning and delivery without anything falling through the gap.
- Engagement planning
- Scope definition
- Delivery coordination
- Client communication
- Documentation
Owns
Scope
What is in the engagement, what is not, and what a change to it costs.
Timelines
What was committed, what moved, and why you heard about it early.
Communication
Every update in writing, and an answer that does not wait for a meeting.
You will hear from her when
Scope or a date changes — before it changes, not after.
Why two
There is no third person.
Most of what a larger team spends its day on is moving information between its own members. Two people have nowhere to move it to — the whole engagement fits inside one conversation, and it stays there.
It is also why the AI matters. The volume a third and fourth hire would have absorbed is absorbed by frontier models instead, under review by the engineer whose name goes on the release.
Not on your project
- An account manager
- A delivery lead
- An offshore build team
- A junior learning on your codebase
You brief Obie and Priscilla. Nothing is handed to anyone else.
Work with us
Talk to the people who will do the work.
There is nobody else to be passed to. Ask about architecture and you are talking to Obie; ask about scope or timing and you are talking to Priscilla. Same two people, first call to release.