[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgmIEcpLAoMfK8d56Rec8w9d8-vSGeefhUXZ2T2JDd9o":3},{"item":4},{"id":5,"idKnowledge":6,"slug":7,"title":8,"description":9,"bodyMarkdown":10,"bodyHtml":11,"author":12,"date":13,"createdAt":14,"topics":15,"image":18,"hasDownload":19,"fileName":20},"26","52DA7FCF-BD2B-6A4D-B739-0B7A21814A2F","necessity-driven-development-bouw-alleen-software-die-echt-nodig-is","Necessity-Driven Development: build only the software that's truly needed","Discover how the Loggix manifesto 'Necessity-Driven Development' helps entrepreneurs and FileMaker developers make better software decisions in the AI era.","**Stop building what's possible. Build what's necessary.** That is the essence of Necessity-Driven Development (NDD) — the philosophy that Loggix founder Jeroen Lutmers describes in the [Loggix Manifest](https:\u002F\u002Floggix-manifesto.vercel.app\u002F). In a world where AI makes everything *possible*, the real challenge is: knowing what you *don't* build.\n\n## What is Necessity-Driven Development?\n\nNDD is an approach in which every software decision starts with one central question: **is this truly necessary?** Not: can it be done? Not: does someone want it? But: does it solve a concrete, proven problem?\n\nThis sounds simple, but it is a direct response to a growing issue: as AI tools make building software faster and cheaper, the temptation grows to stack features, integrations, and automations — even when the business case is razor-thin.\n\n## Why is this relevant for entrepreneurs?\n\nMany companies invest in custom software or ERP extensions based on enthusiasm rather than necessity. The result:\n\n- Systems that are too complex for daily use\n- Maintenance that costs more than the solution delivers\n- Teams that work around the system instead of within it\n\nNDD forces you to first clearly define the *problem* before thinking about a solution.\n\n## Why is this relevant for FileMaker developers?\n\nFileMaker makes it tempting to build something quickly. But speed is no excuse for unnecessary complexity. NDD helps developers to:\n\n1. **Recognise scope creep** before it sneaks into the database\n2. **Have better conversations** with clients about what they *need* vs. what they *want*\n3. **Deliver more sustainable solutions** that are still maintainable 3 years from now\n\n## How do you apply NDD in practice?\n\nThe approach is concrete and applicable to any software project:\n\n1. **Formulate the problem without a solution** — write down what is going wrong without naming a system yet.\n2. **Quantify the pain** — how much time, money, or errors does the problem currently cost?\n3. **Test the necessity** — does the proposed software directly solve this, or does it address a symptom?\n4. **Determine the minimal solution** — what is the smallest system that eliminates the problem?\n5. **Build, measure, decide** — deliver something small, measure the impact, and then decide whether expansion makes sense.\n\n## The role of AI in NDD\n\nAI accelerates building, but changes nothing about the question of *what* you build. On the contrary: precisely because AI makes it easier to generate features, the discipline to say *no* becomes more valuable. NDD gives that discipline a name and a framework.\n\nAt Loggix we apply this in FileMaker custom work, ERP projects, API integrations, and AI integrations: always starting from the question of whether the investment covers a proven necessity.\n\n## Want to know whether your software idea is truly necessary?\n\nLoggix is happy to think along with you. Whether you are an entrepreneur with a concrete challenge or a FileMaker developer looking for a sharper approach — [get in touch](https:\u002F\u002Fwww.loggix.nl\u002Fcontact) and we will look together at what is truly needed.","\u003Cp>\u003Cstrong>Stop building what's possible. Build what's necessary.\u003C\u002Fstrong> That is the essence of Necessity-Driven Development (NDD) — the philosophy that Loggix founder Jeroen Lutmers describes in the \u003Ca href=\"https:\u002F\u002Floggix-manifesto.vercel.app\u002F\">Loggix Manifest\u003C\u002Fa>. In a world where AI makes everything \u003Cem>possible\u003C\u002Fem>, the real challenge is: knowing what you \u003Cem>don't\u003C\u002Fem> build.\u003C\u002Fp>\n\u003Ch2>What is Necessity-Driven Development?\u003C\u002Fh2>\n\u003Cp>NDD is an approach in which every software decision starts with one central question: \u003Cstrong>is this truly necessary?\u003C\u002Fstrong> Not: can it be done? Not: does someone want it? But: does it solve a concrete, proven problem?\u003C\u002Fp>\n\u003Cp>This sounds simple, but it is a direct response to a growing issue: as AI tools make building software faster and cheaper, the temptation grows to stack features, integrations, and automations — even when the business case is razor-thin.\u003C\u002Fp>\n\u003Ch2>Why is this relevant for entrepreneurs?\u003C\u002Fh2>\n\u003Cp>Many companies invest in custom software or ERP extensions based on enthusiasm rather than necessity. The result:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Systems that are too complex for daily use\u003C\u002Fli>\n\u003Cli>Maintenance that costs more than the solution delivers\u003C\u002Fli>\n\u003Cli>Teams that work around the system instead of within it\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>NDD forces you to first clearly define the \u003Cem>problem\u003C\u002Fem> before thinking about a solution.\u003C\u002Fp>\n\u003Ch2>Why is this relevant for FileMaker developers?\u003C\u002Fh2>\n\u003Cp>FileMaker makes it tempting to build something quickly. But speed is no excuse for unnecessary complexity. NDD helps developers to:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Recognise scope creep\u003C\u002Fstrong> before it sneaks into the database\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Have better conversations\u003C\u002Fstrong> with clients about what they \u003Cem>need\u003C\u002Fem> vs. what they \u003Cem>want\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deliver more sustainable solutions\u003C\u002Fstrong> that are still maintainable 3 years from now\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>How do you apply NDD in practice?\u003C\u002Fh2>\n\u003Cp>The approach is concrete and applicable to any software project:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Formulate the problem without a solution\u003C\u002Fstrong> — write down what is going wrong without naming a system yet.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quantify the pain\u003C\u002Fstrong> — how much time, money, or errors does the problem currently cost?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test the necessity\u003C\u002Fstrong> — does the proposed software directly solve this, or does it address a symptom?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Determine the minimal solution\u003C\u002Fstrong> — what is the smallest system that eliminates the problem?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Build, measure, decide\u003C\u002Fstrong> — deliver something small, measure the impact, and then decide whether expansion makes sense.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>The role of AI in NDD\u003C\u002Fh2>\n\u003Cp>AI accelerates building, but changes nothing about the question of \u003Cem>what\u003C\u002Fem> you build. On the contrary: precisely because AI makes it easier to generate features, the discipline to say \u003Cem>no\u003C\u002Fem> becomes more valuable. NDD gives that discipline a name and a framework.\u003C\u002Fp>\n\u003Cp>At Loggix we apply this in FileMaker custom work, ERP projects, API integrations, and AI integrations: always starting from the question of whether the investment covers a proven necessity.\u003C\u002Fp>\n\u003Ch2>Want to know whether your software idea is truly necessary?\u003C\u002Fh2>\n\u003Cp>Loggix is happy to think along with you. Whether you are an entrepreneur with a concrete challenge or a FileMaker developer looking for a sharper approach — \u003Ca href=\"https:\u002F\u002Fwww.loggix.nl\u002Fcontact\">get in touch\u003C\u002Fa> and we will look together at what is truly needed.\u003C\u002Fp>\n","Jeroen","2026-06-11",1781191272000,[16,17],"FileMaker","AI","\u002Fapi\u002Fknowledge\u002Fimage\u002F26\u002F?v=701ee677aaf4",false,""]