We built Kelpmont because the best staffing decisions aren't made with data — yet.
Management consulting runs on judgment. Partners and practice leads make staffing decisions that determine whether an engagement succeeds or fails — and they make those decisions on a combination of experience, recency bias, and whoever is available this week. The pattern data that could inform those decisions sits archived in every firm's CRM, organized by engagement and untouched after close.
This is not a technology problem. It is a translation problem. The engagement history is there. The consultant-client chemistry patterns are there. The at-risk signals are there — visible in billing cadence and meeting attendance weeks before anyone escalates. Kelpmont's purpose is to surface that record at the moment the decision is being made, in a format that a practice lead can act on in the time they actually have.
We are not a staffing automation tool. Kelpmont does not make staffing decisions and does not score consultants as individuals. It surfaces patterns from your firm's own history so that the humans making the decision can make it with more than memory.
Sarah Mitchell
CEO & Co-Founder
Sarah spent eight years in consulting operations — first at Whitmore Consulting Group, where she managed resource allocation across the strategy practice, then at Ashford Partners, where she served as VP of Operations for a firm of 180 consultants. In both roles, she was the person whose job it was to answer the question partners most often couldn't: which consultant, for which engagement, and why.
The answer was almost always the same. Practice leads called on the people they remembered most recently. Managing directors worked from status reports that described what had already happened. Operations teams spent two to four hours per week extracting utilization data that existed in Salesforce — but in a form that required manual assembly before it was readable as a staffing input. In 2024, Sarah co-founded Kelpmont to close that translation gap. The product started as an internal script she ran against her own CRM. It became a company when three other practice leads at peer firms asked if they could use it.
The team.
Daniel Reyes
Head of Engineering & Co-Founder
Previously built data ingestion and reporting infrastructure at Projector PSA. Joined Kelpmont at founding. Leads platform architecture, CRM connector development, and pattern engine design.
Olivia Farrow
Head of Product
Four years as a consultant at Strathmore Advisory Group before moving to product. Responsible for signal design and how Kelpmont surfaces evidence without overstating confidence.
Marcus Webb
Head of Customer Success
Seven years in consulting operations and resource management before joining Kelpmont. Leads client onboarding — including the initial CRM connection and first pattern report review with each firm's practice team.
What we believe.
Evidence over instinct.
Instinct is built from experience that data can't replicate. But instinct is also bounded by what you personally remember and when you last worked with whom. Evidence extends the range of what a practice lead can hold in mind. Kelpmont doesn't replace judgment — it gives judgment a longer memory.
Confidence, not certainty.
No staffing decision is a guarantee, and Kelpmont doesn't claim otherwise. We surface signals that increase the confidence of a decision — not predictions that claim to know the outcome. The distinction is not subtle. Tools that overclaim lose credibility with senior practitioners the first time they're visibly wrong.
Tools that earn their place.
A managing partner with twenty years of consulting experience will not change how they staff engagements because a piece of software recommends it. They might change when the software shows them a pattern they recognize as true and hadn't been able to see clearly before. Kelpmont is built to earn that moment, not to mandate the decision.
Get in touch.
[email protected]
+1 (415) 555-0184 · 425 Market Street, Suite 800, San Francisco CA 94105