Victor Crum

When we first launched, we operated lean. We improvised our tools, worked out of tiny spaces, and every dollar spent was strictly tracked. Then right after our first funding round, we upgraded to expensive software suites, hired too quickly, and spent heavily on premium perks. Instead of accelerating our growth, it dramatically raised our burn rate and left us scrambling before reaching product-market fit.
How do you maintain a frugal, resourceful mindset across the company once fresh capital hits the bank account?

I maintain Termexo. This update is about a small interaction with a useful consequence: ask one coding agent to send work to another terminal, then read back the result.

AI-assisted capability diagram, not a screenshot.

Last weekend I tried Lovable to build a simple habit tracker, and the starting results were mind-blowing. But by Thursday, every small tweak started breaking existing features I wasn't even working on. Prompts became exhausting, and my patience was tested.

I started attaching a small constraint document: a brief summary of the app's goals, explicit restrictions on what it shouldn't alter, and a record of all error-free screens. I paste this right at the start of every big prompt.

It s far from perfect, but it reduced unexpected code breakages significantly.

Do you paste guidelines with your prompts, or do you rely on starting from scratch each time?