Our story
Alpha to Omega. Beginning to end.
AlphaOak was incorporated in January 2025. The company is young and the practitioners are not — 20+ years each, hundreds of SAP EAM projects, three continents.
That is the whole proposition: senior people, a single platform, and small teams.
The name
An A inside an Ω, and a tree between them
The first and last letters of the Greek alphabet, and therefore of everything that can be spelled with it. Notice what the mark actually does: the A does not stand next to the Ω — it stands inside it. The beginning is held by the end.
Around them both, an oak: gold roots below, gold branches and green leaves above. Start to finish, and the living thing that does the growing in between.
Branches
Growth for our clients, our people, and our communities.
Trunk
Strength of our partnerships.
Roots
Depth of experience and trust.
Go deep rather than wide. That is simply how trees work.
Our values. Our standard.
Five principles. The test is what they cost.
Our values
01 — Action
We move.
Conditions are never perfect. That is the weather, not an obstacle.
02 — Leadership
We step in.
The best idea sets the direction, which means seniority does not.
03 — Precision
We do it right.
Precision is affection for detail, not anxiety about it.
04 — Honesty
We say it straight.
Sometimes we lose the moment in the room to keep the relationship.
05 — Accountability
We own it.
Everything here has somebody’s handwriting on it.
What they cost
Five principles that guide how we think, act and deliver
The test is never whether you can recite them. The test is what they cost.
Our position
Utilities first. One platform. Deeply.
Year one · 2024–2025
Foundation
SAP and Esri partnerships, the team, and the first product IP.
Year two · 2026
Activation
The product suite, the Grove, and the market conversation.
Year three · 2027
Operation
Running as a product company with an advisory practice alongside it.
We are building something meant to last.
Next step
Start with the hardest part
A short conversation about where your SAP, GIS and schedule data stop agreeing — and what it would take to bring them into line.