A letter to professional services.
Professional services is one of the hardest categories to build software for. The work is non-standard. The margins live or die on decisions that rarely get written down. We've been in the room for all of it.
The story behind Servantium
Professional services is the hardest type of business to scale. Every engagement is bespoke to some degree. The pricing lives in someone's head. The delivery knowledge walks out the door when people leave. The margin lives or dies on decisions that were made in a conversation that nobody documented.
This isn't solvable with better spreadsheets. It's solvable with better systems. Systems that treat scope as a first-class object. Systems that connect what you promised to what you delivered to what you charge next time. Systems that make your institutional knowledge durable instead of fragile.
We built Servantium because we've lived on both sides of that problem. We ran the teams. We implemented the tools. We know what breaks down and why.
The pattern never changed. Talented consultants pricing engagements from memory. Scope changes communicated over Slack but never making it to the contract. Delivery teams rebuilding what someone else already built last quarter because nobody wrote it down in a place the next team could find.
Product companies don't have this problem. Every feature, every price change, every customer interaction feeds back into the system. Services businesses deserve the same loop.
We'd seen the PSA tools. They track hours. They don't capture the reasoning behind a scope decision or the lessons from a delivery that went sideways. We'd seen the CRMs. They track deals. They lose the thread the moment a deal becomes a project.
What nobody had built was the connective tissue: a system that carries context from the first client conversation through scoping, pricing, delivery, and back into the next engagement. A system that actually remembers.
There's no shortage of companies selling AI agents that sit on top of your knowledge base and answer questions. That's not what this is. We're not building a chatbot that summarizes your Notion docs or an assistant that can tell you what someone said in a meeting. We're building your services business's action layer. The system that structures your engagements, connects your decisions to your outcomes, and gives every AI tool you deploy something worth running on. Better work, done faster, with a team that gets smarter every time.
We didn't want to build another tool that bends to chaos. We wanted to build one that creates structure.
The name comes from servare, the Latin root meaning to keep, to preserve what was promised. The suffix -ium reads two ways at once. Classical: a place where something happens, like a gymnasium or auditorium. Modern: a foundational element, like titanium or platinum. Servantium is both. The place where service happens, made of the foundational element of doing that work well.
We're building an operating system for services teams. Not a dashboard. Not a time tracker. A system that encodes how your team works, so it can work better every time.
Technology should amplify human expertise, not replace human judgment. Services are relationships. We're just giving them better memory.
Meet the founders
Two founders. One ran the delivery organizations. One built the platforms they ran on.
Christopher Veale
Christopher has spent his career leading delivery teams across life sciences, legal technology, and enterprise SaaS. He's owned P&L responsibility at every stage, managed global teams, and worked through every variety of engagement where the scope becomes fiction by week four.
He has watched excellent teams with excellent people lose money on work they should have won, and win work they were never going to deliver profitably. Servantium is the answer to one question: what if the pricing, scoping, and delivery knowledge those people carry in their heads became the engine the entire organization runs off of?
Biomedical Engineering, Drexel University.
Maxwell Friel
Maxwell has spent his career on both sides of the professional services equation. He's built the platforms that delivery teams run on and run the delivery organizations that implement them. His background spans bad data models in regulated industries, VP-level engineering and services leadership, and the kind of systems thinking you develop when you've been both the person who built the tool and the person stuck using it.
He holds an M.S. in Artificial Intelligence and Machine Learning from Drexel University and brings hands-on depth in AI engineering, Python, cloud architecture, and systems design. He's building the platform he wished he'd had at every previous company.
Build the system that turns a services team's knowledge into a lasting advantage. Help every team scope faster, price smarter, deliver better, and never lose what they've learned.
How we operate
The principles that drive every decision we make.
Startup Speed
Ship fast. Prove it weekly. Every release makes the product meaningfully better than it was on Friday. If it doesn't, it doesn't ship.
Customer First
Every feature solves a real problem for someone doing real work. Talk to customers constantly. Let their workflows shape the roadmap. No vanity features. No building because a competitor has it.
Relentless Iteration
Treat feedback as a gift. The version shipping today is the worst version that will ever ship. That's the standard, not a caveat.
Join our founding partners
We're working with a small number of services teams who believe their operational knowledge deserves better than spreadsheets and tribal memory.