Software that fits your business. Exactly.
Web applications, internal tools and platforms, designed and written by the person you talk to. You own the code, the data and the keys from day one.
It is right when.
- Your operation lives in a spreadsheet, or in one person’s head
- You are bending an off-the-shelf tool to do something it was never meant to do
- The part the tool cannot do is the reason you are in business
- You pay monthly for software you will never own or export
- An AI tool built your first version, and now it has to be real
If a platform genuinely fits your needs, use the platform. I will say so on the first call, and point you to it.
“Off-the-shelf software is something you rent forever. Custom software is an asset you own.”
How a project runs.
- Discovery
We map the problem and the one outcome that matters most.
- Fixed-scope first phase
One outcome, one price, agreed up front.
- Demos at every step
You see working software, not status reports.
- You own everything
Your repository, your keys, your data.
- Decide at each milestone
Continue, pause or stop, and keep what you paid for.
Built this way.
- customs-invoice.com
A spreadsheet only one person understood, turned into a product.
My product - Blockal Ravid
A compliance chore, turned into a quiet sales asset.
Built for Blockal Ravid - Loxu
One sharp pain, one focused product.
My product
Read before you decide.
In-depth guides, each with a working Field Kit.
- Custom Software for US Businesses: Build vs Buy, Real Costs, and Timelines
A practical, no-hype guide for US small and mid-size businesses deciding whether to build custom software, what it really costs, how long it takes, and how to d…
Includes the Cost and Scope Scorecard - How to Secure an Admin Panel: Google Auth, 2FA, and Sessions on Vercel
A technical guide to locking down an admin panel when both your client app and admin run on Vercel. Google sign-in with an allowlist, real 2FA, why httpOnly coo…
Includes the Admin Security Checklist - From Idea to MVP: Scoping a First Phase That Pays for Itself
A practical guide to turning a software idea into a first phase that ships and pays for itself. Finding the one workflow worth building first, cutting scope to …
Includes the MVP Scoping Worksheet - Escaping No-Code Lock-In: Moving From Bolt or Lovable to Code You Own
A technical guide to graduating from no-code AI builders to software you own. Why builders are great until they are not, the signs you have outgrown one, what o…
Includes the No-Code Exit Checklist - Database Design for Non-DBAs: A Practical Technical Guide
A practical guide to designing a database you will not regret. Modeling real entities and relationships, choosing keys and types, letting the database enforce i…
Includes the Schema Design Checklist - Don't Lose Your Data: Backups and Disaster Recovery for Small Businesses
A technical guide to backups and disaster recovery that actually work. Why an untested backup is not a backup, what to back up, the 3-2-1 rule, point-in-time re…
Includes the Backup and Recovery Checklist
Questions.
How long does a custom build take?
It depends on scope. Simple automation tools can take 2 to 4 weeks; a comprehensive business platform typically takes 2 to 4 months. The first phase is always small, fixed in scope, and priced up front.
Who owns the code?
You do, from the first commit. The repository, the hosting account and the keys are yours, so there is no lock-in holding you to me.
Our AI tool already built a prototype. Do we start over?
Rarely. Most of what Lovable, Replit or your own prompts produced can stay. The work is making it safe, owned by you and connected to the business, and the AI-Build Audit tells you exactly which parts must change first.
What if we were burned by a developer before?
That is more common than it should be. It is why I work in small fixed-scope milestones with demos before invoices. You never fund a black box.