A tool that fits
Dashboards, portals, and web apps built around the way your team already works.
Sandia Software Services · Albuquerque, New Mexico
Software projects get unstuck here.
New products, inherited codebases, and the work between them—web, mobile, automation, and AI systems that need to function in the real world.
No perfect brief required. Start with what exists.
Where we come in
A new product needs a first release.
A stalled project needs a way forward.
A legacy system needs careful modernization.
Start with the real situation. Build from there.
Maybe this sounds familiar
Your business has outgrown the tools you started with.
Important work gets buried in email threads, spreadsheets, half-connected apps, and processes that only one person understands. Sandia helps make the next version clearer.
An app people use
Mobile and wearable products, from first idea through the release details.
Less busywork
Automations that stop your team from copying the same information all day.
AI with a job
Triage, drafts, summaries, and follow-up—with a person still in the loop.
Some of the work behind this
Real products, not demo screens.
Marketing automation
SEOMelon
Operator-facing tools for SEO research, diagnostics, content workflows, and outreach.
Mobile and wearable
StepMelon
A product family spanning mobile UX, watch experiences, backend work, and release execution.
Community and events
AP-OD
A multi-surface product involving native apps, web integrations, deployments, and live troubleshooting.
New work or inherited work
I can meet a project wherever it is.
Some projects begin with a blank page. Others come with years of decisions, a tired codebase, or a previous team that stopped showing up. My work with AP-OD has included both: building new capabilities and taking over stalled or legacy work to make it useful again.
01 · New product work
From idea to something real
Shape the first useful version, make the important tradeoffs, and get it in front of real people.
02 · Project rescue
When the work has stalled
Recover context, identify what still matters, and turn a vague backlog into a path forward.
03 · Legacy modernization
Improve without throwing it away
Understand the existing system, protect what works, and replace the risky parts in a sensible order.
04 · Technical ownership
Keep the project moving
Help with decisions, integrations, releases, troubleshooting, and the parts nobody else has time to own.
This is not about judging the last team. It is about making the next step clear.
Understand the situation
Start with the workflow, the constraints, and the parts that are not working.
Build the useful part
Choose a scope that can actually be finished, adopted, and improved.
Keep it moving
Stay close to the decisions, the progress, and the tradeoffs.
No perfect pitch required
Have a process that is driving you crazy?
Bring the plain-English version. We will help identify the right first move.