Leadership
Most leadership pages list titles. Titles tell you very little about who to call when something is wrong, so this one lists what each person actually owns and can be held to.
Chief Executive Officer
Denver, Colorado
Runs the commercial side of the firm from Denver. Came from enterprise software sales and spent long enough on the buying side to be unsentimental about how badly most engagements are scoped before anyone writes code.
Founder and Chief Technology Officer
Lahore, Punjab
Started the firm on the argument that most software projects fail for commercial reasons rather than technical ones, and that the fix is a written scope and a fixed price rather than a better methodology. Owns the technical standard on every engagement and still takes the first call on most of them.
Director of Delivery
Austin, Texas
Responsible for the number in every proposal. Fixed price means an estimate that is wrong is our problem, which makes this the role with the least room to be optimistic and the most leverage on margin.
Head of Product
Seattle, Washington
Runs Open Lance and BotUp as products rather than as showcases, including the uncomfortable decisions about what the services business subsidises and for how long.
How we are organised
The structure exists to keep the distance between a client and the person writing their code as short as it can be. Every layer we removed was a layer that translated.
The person on your first call could work on the project. They are allowed to tell you we are the wrong firm, and they do.
You know who is on your project and they stay on it. Rotation happens for holiday and illness, and you are told when it does.
There is no account management tier to route around. If the engagement is in trouble, the person who priced it hears about it directly.
Not a transition team reading documentation for the first time. The handover is done by whoever wrote the thing being handed over.
Where we are
Registered in Denver, Colorado. The engineering floor, and most of the building, is in Lahore.
Work with us
Next step
No discovery call with a salesperson, no deck. A senior engineer reads what you send and replies with a real assessment, including when we think you shouldn’t build it.
Certified, partnered and awarded
1/7
Start a project
A senior engineer reads every one of these, and replies within one business day. Nothing here goes to a sales sequence.
To begin
One click. It decides what we ask next.
The problem
One line is plenty. This is the part an engineer actually reads first.
Today
Pick any that apply.
Timing
A real deadline changes the design. An arbitrary one does not.
Size
A range is fine. It shapes what we propose, not what we charge.
Your side
It changes whether we lead, embed, or advise.
Last one
A senior engineer replies within one business day. No sequence, no newsletter.
How would you rather hear back?
Sent
Here is what you told us, and what happens next.