Apps, integrations, migrations, automation and websites — built around how your business actually runs, not around a template. Fixed quotes. Working software every week. You own everything.
Each starts the same way: understand how the business runs, then build the smallest thing that fixes the real problem.
You need software that doesn't exist yet: a product, a customer portal, or a tool your team uses every day.
Designed and built end to end — from the first screen to the App Store or your team's browser — on a stack that will still be easy to maintain in five years.
The tools you already pay for don't talk to each other, so someone re-types the same data three times.
The connections built and monitored: when something happens in one system, the right thing happens in the others.
You've outgrown a system — or it's about to be shut off — and moving feels riskier than staying.
A planned move with the data checked on both sides, run alongside the old system until the new one is proven. No lost records, no lost day.
People spend hours on work a machine should do: follow-ups, reports, data entry, document prep.
The repetitive work taken off people's plates, with AI where it actually helps and plain code where it doesn't. Every automation reports what it did.
Your site is out of date, hard to change, or doesn't bring in customers.
Fast, custom-built, easy to update — with booking, quotes or payments wired in, and a care plan after launch so you never think about it.
The numbers exist, but they live in five places and nobody trusts the version in the meeting.
One live view pulled from the sources — sales, operations, finance — so decisions get made on today's numbers instead of last month's export.
Not sure which one you need? Describe the problem. I'll tell you what it takes — and if software isn't the answer, I'll say so.
Describe the problemUnderstand the operation, find what's actually in the way, build the thing that removes it.
Understand before scoping, scope before building — so the work stays aimed at the real problem, not the obvious one.
What the business does, where work slows down, and what done looks like. You don't need a spec. Twenty to thirty minutes is usually enough for me to see the shape of it.
What gets built, what it costs, and when it ships — in writing, before any money changes hands. Bigger projects are split into phases so you see the cost of each before committing to the next.
Working software every week, not a reveal at the end. You try it as it comes together and steer while changes are still cheap.
Deployed, documented, and walked through with your team. You own the code and the accounts. If you want someone on call for changes and upkeep, that's a monthly retainer, not a lock-in.
A fixed price per project, quoted in writing after the first call. Smaller builds — a website, an integration, an automation — usually land in the low thousands. Apps and migrations are scoped in phases, so you see the cost of each phase before it starts and nothing is open-ended.
A website or a single integration: two to four weeks. An internal tool or a migration: one to three months, in phases. An app: longer, and planned that way. You get a date with the quote and working software every week in between.
Yes. The code, the accounts, the domain, the data — all of it is in your name from the start. If we stop working together, nothing stops working.
No, it's the normal starting point. Describe what's slowing the business down and I'll tell you what it would take — sometimes that's an app, sometimes a two-day integration, and sometimes it isn't software at all. I'll say so either way.
Usually, and I prefer to. Most projects connect to or build on the tools you already use — your CRM, your accounting software, your booking system — rather than replacing them. Replacement is for when something is genuinely in the way.
Whatever fits the job and will still be easy to maintain in five years: TypeScript and React for the web, Swift for iOS, Python for data and automation, Cloudflare or AWS for hosting, and AI models where they actually help. No exotic choices you'd struggle to find someone else to support.
Maryland. Most clients are in the DMV, and everything happens over calls, screen-shares and email, so location doesn't matter.
Most of the work is learning how a business actually runs — not how it’s described in a meeting, but how work moves through it day to day. The problem worth solving is rarely where people first point. Once that’s clear, the build is the easy part.
I’m Grant. Computer science at the University of Maryland, two and a half years building production software for complex engineering systems, and my own products shipped since — including Lerf, an iOS app on the App Store. You’ll work with me directly. You get my number.
Tell me what's slowing the business down or what you're trying to build. I'll reply within one business day with what it would take — or a few questions if I need them.
No pitch. If software isn't the answer, I'll tell you.
Prefer to text or call? Skip the form — both reach me directly.