Skip to main content

Company file

Built to Go First

We are a software boutique for work that requires judgment before it requires code. We help clients make sense of difficult problems, find a credible path forward, and build the software to pursue it.

Our mission is to give our clients greater freedom of action: the capability to pursue an opportunity, overcome a constraint, or make a consequential change without being held back by their technology.

That takes technical depth and a willingness to move into unfamiliar territory. It also takes the discipline to distinguish a promising idea from an expensive distraction.

Schedule a meeting
01Mission

Understand the Ground

Before we recommend a solution, we need to understand what it must accomplish. That means learning how your business operates, where the constraints are, and what happens if our assumptions prove wrong.

Sometimes the most valuable early work is a prototype. Sometimes it is a difficult question, or an honest recommendation to build less. We want to discover what matters while there is still time to change course.

02Mission

Give People Room to Act

We believe the people closest to a problem should have the authority to address it. Clear objectives and shared context let a small team make sound decisions without routing every detail through a hierarchy.

That autonomy carries an obligation: explain your reasoning, surface uncertainty, and ask for help before a manageable problem becomes someone else's emergency. Independent judgment works when people can trust one another.

03Mission

Put Our Strength Where It Matters

A small firm has to be deliberate about where it commits its attention. We take on work where our expertise can materially change the outcome, and concentrate our effort on the decisions that carry the most consequence.

We value ingenuity, including the ingenuity to recognize when an ordinary solution will do. Complexity has to earn its place. Our clients inherit what we build, along with the cost of operating and maintaining it.

04Mission

Stay Accountable to the Purpose

A specification records what we think is needed. As the work progresses, we may learn otherwise.

We consider it our responsibility to raise that discrepancy, explain the tradeoffs, and help decide what should change. Completing the agreed work matters. So does being candid when that work no longer serves the objective.

The same standard applies within our team. We share knowledge, make mistakes visible, and help each other resolve them. Heroics are a poor substitute for colleagues who can depend on one another.

05Mission

Where This Comes From

Our founder's prior service in the US Cavalry helped shape this outlook: understand the situation, exercise initiative, and remain responsible to the people relying on you.

Those convictions inform how we approach software and how we work with our clients. We intend to leave them with systems they can understand, capabilities they can sustain, and more room to decide what comes next.

06Background

Trevor Grant: judgment and implementation.

Founder Trevor Grant is an AI and open-source systems engineer and technical leader. His work spans production machine learning, developer infrastructure and agent tooling. That experience informs how we weigh technical choices, explain tradeoffs and carry decisions through to working software.

Selected record

Builder history

Lead author
Kubeflow for Machine Learning: From Lab to Production. The book record describes coordinating a changing platform and building a practical ML workflow—not just selecting tools.
Open source
Apache Software Foundation member and Apache Mahout PMC member. His Mahout / QuMat work connects project stewardship with hands-on backend abstraction.
AI Alliance tooling
Built AgentLabUI and later rewrote it into Gofannon. The project record explains the work of turning agent workflows into usable interfaces.
07Team

Built around shared responsibility.

Our core team works alongside longstanding collaborators. The principles above apply to all of us: understand the objective, exercise judgment, share what we learn, and remain accountable to one another and our clients.

08Artifacts

The archive is part of the proof.

Old projects are kept because they show how the work was learned: agent tooling, production ML writing, open-source systems, generative experiments, civic automation, rewrites, dead ends, and useful failures.

Artifact drawer

Prior work preserved

Shows
What was tried, built, rewritten, deprecated, and learned from.
Inspect Artifacts
09Fit

Start with the work that matters.

Tell us what you are trying to accomplish, what is getting in the way, and which decisions need a clearer path. You do not need a finished specification.