Denver, Colorado / Custom software
Good software.
Built around your business.
Turn a complicated workflow into a tool people want to use. We design and build custom software with clear decisions at every step.

01 / What we build
Your workflow.
The right software.
Start with what needs to work better. Choose the technology that makes sense for the job.
Web applications
Customer portals, internal tools, and platforms that turn a complicated workflow into a useful everyday product.
02Mobile apps
Purposeful mobile experiences for people in the field, on the move, or working away from a desk.
03APIs & integrations
Bring the tools you already use together with clear data flows, dependable integrations, and practical automation.
04Legacy modernization
Improve an existing application in manageable steps, with a plan for its data, dependencies, and daily users.
A focused first release or a careful upgrade to an existing system.
Find your starting point02 / How we work
No mystery.
Just a clear next step.
Good collaboration means you know what’s happening, what needs a decision, and what comes next.
- 01
Understand
Map the problem, the people, and the constraints before choosing a solution.
- 02
Make it tangible
Explore the important screens and workflows. Put the decisions in front of you.
- 03
Build & review
Deliver in small increments, demonstrate progress, and resolve questions as they arise.
- 04
Launch deliberately
Check real scenarios, prepare the release, and agree how to handle the unexpected.
- 05
Leave it usable
Make the code, the setup, and the operating knowledge part of the delivery.

03 / The Letter99 approach
Care about the work.
Explain the thinking.
A useful product starts with understanding the people who will use it.
We value direct conversations, practical choices, and software that can be understood after it ships. That means discussing the tradeoffs, writing down the decisions, and making handover part of the work.
What that looks like in practice04 / Quality you can check
Good work leaves
a clear trail.
Know what to review, what has been agreed, and what you will need to operate the software after launch.
Make “done” concrete.
Define the important tasks, the expected behavior, and the exceptions before reviewing a release.
02 / ReviewSee the work in use.
Review working software against the agreed scenarios. Keep unresolved questions and release decisions visible.
03 / HandoverLeave it understandable.
Agree the code, access, documentation, and operating knowledge that belong in the delivery.
Practical expectations for a software project.
Explore our quality approachLet’s talk software
Start with the problem.
A new idea, a tangled workflow, or software that needs a second life. Tell us what you’re working through.