Build or buy an internal tool? Compare the whole responsibility
Build or buy internal software by comparing fit, ongoing ownership, and opportunity cost. Use a short worksheet instead of comparing subscription and coding time.
Read the field noteField notes / 8 articles
Keeping software alive
The work that begins after the first working demo.
Building software is one decision. Maintaining it is another.
Building a prototype and operating software are different commitments. Map recurring ownership, dependencies, support, and recovery before promising more.
Read the field noteWhat if your customer vibe codes your product?
When a customer can build a version of your product, compare ownership costs and outcomes. Find the job they still want a supplier to manage reliably.
Read the field noteReliable integrations can be a startup advantage. Here is the hard part.
Integration reliability means handling retries, duplicates, stale state, and recovery. Start with one important connection and make its failures understandable.
Read the field noteGive customers an exit plan before asking them to trust your startup
A clear software exit plan reduces the fear of choosing a young company. Explain exports, access, continuity, deletion, and the limits of your promise.
Read the field noteHow to budget maintenance time as a solo founder
Budget maintenance in hours and cash, then compare it with your actual week. Use a simple capacity worksheet that includes support and interruptions.
Read the field noteTechnical debt before product-market fit: what can wait?
Before product-market fit, accept reversible shortcuts that accelerate learning. Keep a debt register and protect access, data integrity, and recovery.
Read the field noteA production checklist for your vibe-coded MVP
Before real customers rely on a vibe-coded MVP, verify ownership, access, data handling, recovery, and the critical workflow. A demo is only the start.
Read the field note