# Undefined Software ## You need software built. I build software. Source: https://undefined.company/ I'm an independent developer with ten years of production experience. You bring a problem — an idea that needs building, a system that's stuck, a team that's short-handed — and I build the thing and hand it over working. ### What I do - **Build it from scratch** — You have an idea and no engineering. I take it from nothing to something running in production that real people use. - **Finish what's stalled** — A project ran out of runway, or the developer left. I pick up the existing code, work out what's there, and get it over the line. - **Fix what's breaking** — Slow, fragile, falling over under load, or terrifying to deploy. I find out why and make it boring again. - **Add capacity** — Your team is good but underwater. I work alongside them for a stretch and ship features without needing to be managed. ### Why work with me - **You get the senior person** — Agencies sell you a principal and staff the work with juniors. I'm the one who talks to you and the one who writes the code. - **Solo means fast** — No handoffs, no status meetings, no internal politics. Decisions happen in the time it takes me to make them. - **Priced per piece of work** — I break work into chunks and quote each one. Simple, low-risk work is cheap. You always know what the next step costs before it starts. - **Straight answers** — If your idea has a problem, I'll tell you during the quote, not three invoices in. If it's not work I'm good at, I'll say so. ### What I don't do I don't build mobile apps, and I'm not a designer — if you need a visual identity or a polished interface designed from scratch, you want a designer, and I'm happy to work alongside one you hire. I also don't take on work I don't think will succeed. If the budget doesn't fit the scope, or the problem isn't really a software problem, I'd rather tell you that up front than take the money. ## How we'd work together Source: https://undefined.company/services No open-ended retainers and no surprise invoices. Work gets broken into pieces, each piece gets a price before it starts, and you decide whether to keep going after each one. ### The process - **1. A call** — Thirty minutes, free. You describe the problem. I ask questions and tell you honestly whether it's something I can help with. - **2. A written scope** — I write down what I understand you need, broken into chunks, with a price and a rough timeline for each. Nothing starts until you've read it and agreed. - **3. Build, in the open** — I work in chunks and show you progress as it lands, not at the end. If something turns out harder than quoted, you hear it immediately. - **4. Handover** — You get the code, the deploy pipeline, and documentation good enough for the next developer. No lock-in and no dependency on me. ### How pricing works I price per chunk of work, not per hour, and the price reflects complexity and risk. A well-understood piece of work with a clear answer is cheap. Something genuinely uncertain — where the honest answer is that it needs investigation before anyone can estimate it — costs more, and I'll tell you which one you're looking at. This means you're never buying an open-ended commitment. You approve one chunk, you see the result, and you decide whether to approve the next one. If you want to stop, you stop, and you keep everything built so far. ## About Source: https://undefined.company/about Undefined Software is one person. I've spent ten years building production software — at industry-leading consultancies, where I learned how to work with clients and hand things over properly, and at venture-backed startups, where I learned how to ship under real constraints. ### How I work I favor small, reversible steps over big rewrites. Rewrites are how projects die: six months of work, nothing shipped, and the old system still running. I'd rather get something working in front of people early and improve it from there. I write things down. What we agreed, what I found, what I'd do differently. You shouldn't have to hold the state of your project in your head, and you shouldn't lose it when I finish. I'd rather deliver bad news early than defend an estimate. If something is going to take longer or cost more, telling you in week one is worth far more to you than telling you in week six. ### What I build with Mostly web software: TypeScript, modern frontends, APIs, databases, and the infrastructure to run them. I'm comfortable across the stack, including the deployment and operations side that often gets left as someone else's problem. I also use AI tooling heavily in my own work, which is part of why a single person can move quickly on projects that would traditionally need a small team. ## Writing Source: https://undefined.company/writing Notes on building and shipping software — what works, what doesn't, and what I'd do differently. ## Let's talk about your project Source: https://undefined.company/contact Book a free 30-minute call. Bring the problem you're trying to solve — you'll leave with an honest answer about whether it's something I can build, roughly what it would take, and what I'd do first. Email: admin@undefined.company ### What to expect No pitch and no pressure. If I don't think I'm the right person for the work, I'll tell you on the call rather than sending you a quote. If it is a fit, I'll follow up with a written scope broken into priced chunks, so you can decide with real numbers in front of you.