Fix and finish software products

Finish the software that never made it into use

Find what is failing, keep what works, and make the product usable.

Discuss a paid build

01Find the part that is failing before deciding what to rebuild
02Preserve the behavior that already works
03Finish the user task that matters first

Related work

Similar products I built.

03Artist development + music-business discovery

“Post more” is not a plan.

KAI uses the artist’s music, goals and current work to set the next job and follow the evidence. CutLab has produced real audio-and-video output for review. SeenStage lets music businesses search artists by the music, work, momentum and missing proof behind the profile—not just the profile picture. Core pieces work. The two-sided product is still in active development and is not a finished production platform.

SeenStage case study

Real Seenstage artist studio with KAI working from an artist’s public music — KAI finds the artist’s real music, learns who they are, and leads the next move.

02Development control · Windows + Android

Software work should not stop because I leave my desk.

So I built MANTIS. It keeps long development sessions working against the real files, terminals, browsers and tests on my Windows workstation while I control those same sessions from my phone. I can switch projects, read the terminal, send instructions, stop a job and restore the same session from Android. The goal, backups, tests and recovery stay attached to the work. The workstation must remain awake and connected.

MANTIS case study

The Android app opens the same live work still running on the computer.

06Personal and small-business finance

Your bank balance is not permission to spend it.

Karat is being built to calculate a safer number for today from transactions, bills, income, debt and goals—and show the math. The latest anonymous browser check did not return the first planning answer, so this remains a development example.

Karat case study

Real Karat Today screen showing a large Safe to Spend number and the calculation behind it — The answer comes first: today’s number and the exact math behind it.

How I work

Find what slows the work. Build only what removes it.

01Trace the job
Find where time, information, or decisions get stuck.
02Build the fix
Connect the screens, data, and tools the job needs.
03Use it on the job
Use it the same way customers or staff will.

01ClientGet the first build scopedSend me the customer or staff job you are sick of doing by hand. I’ll tell you the smallest paid build worth making, what it must do and how we will prove it works.02Remote roleHire a Full-Stack Product EngineerThe customer does not care which part of the stack broke. I work remotely. I can trace the problem from the customer screen through the backend, data and staff tools, then prove the action where it failed.