I'm Frank. I build software for people who don't have anyone technical on their side.
The people who most need software built are usually the least likely to have someone who can build it well, or tell them what not to build. That gap is why this business exists. I still do the building myself, which is unusual for someone running a software company, and it's deliberate: the advice you get comes from the person who has to make it work.
A career spent building, at every scale.
I came out of RPI in Troy, and learned the trade at scale after it. At OnePay, a venture-backed fintech, I was an engineer on a mobile banking app used by tens of millions of people — software that moves tens of billions of dollars a year. When the software you build is holding someone's money, you learn fast what “ready” really means, and what it costs to get there.
Then I led the engineering team at Huml Health, a healthtech startup building wearable devices for patients going through substance-abuse detox and recovery. Going from one engineer among many at a billion-dollar company to the lead at a tiny startup taught me the other half of the job: making the call, owning the roadmap, and answering for the outcome when there's no one above you to escalate to.
Alongside all of that, I spent five years building software for Preston Center of Compassion, a nonprofit in the Bronx. That's what showed me what I wanted to do. Working with a local, nontechnical organization, you see exactly who your work helps and how much it matters — the impact is right in front of you in a way it never is when you're one engineer among hundreds at a company moving billions.
What I kept noticing was that the people who most needed software built — founders without an engineer, organizations without technical leadership — were the least likely to have anyone who could build it well, or tell them what not to build. They didn't need a big agency, and they didn't need an order-taker. They needed someone who could tell them what to build, what to skip, and what it should cost, and then build it and stand behind it. So that's what I do now.
What I believe about software decisions
Sometimes the answer is to build nothing.
Plenty of problems that look like software problems aren't. Often the fix is changing a process, renegotiating with a vendor, or simply waiting — and saying so out loud is part of what you're paying me for.
Advice is only as good as the hands behind it.
I can tell you what something will really cost because I quoted and shipped that exact work this year — not because I read a report about it. That's why I never stopped building.
Proof, if you want it: I keep a technical blog at matranga.dev ↗ — mostly for other developers.
You should own the plan, not rent it.
Whatever I hand you is written in plain language, tied to no vendor, and yours to take anywhere — including to someone other than me.
Based in New York's Capital Region — and helping build its tech and entrepreneurship community.
I work with clients anywhere. I'm invested in Albany specifically — that's a fact about me, not a limit on who I build for. I put real time into the local ecosystem: organizing events, convening technical people, backing early founders, and showing up for the organizations that keep this region's economy moving.
- Co-founder, 518.codesA community for technical people in the Capital Region — from happy hours and indoor climbing to game jams, hackathons, and tech talks.
- Organizer, 1 Million Cups Capital RegionThe weekly meetup for local entrepreneurs.
- Leadership Capital Region, Class of 2027
- Founding Limited Partner, Good Neighbor Fund Capital Region
- Member, Capital Region Chamber & Rensselaer County Regional Chamber
If you're weighing a build, tell me about it.
Book a free call and you'll get me — no form, no one in between. I'll tell you whether I'm the right person for what you're facing.
Prefer to write? frank@matrangacode.works
Or call (518) 217-8298 · find me on LinkedIn →