# Got an app idea, but no one to build it? Here's where to start. URL: https://up2.digital/solutions/idea-no-app > An idea that only exists in your head can't be tested, shown to anyone, or shown to work. The first useful step is smaller than you think. ## Why it happens A good idea stalling isn't a sign it's a bad idea. It's usually a sign of a missing, specific next step. ### "Build an app" sounds like a huge, vague commitment Without breaking it down, an app idea feels like it needs a technical co-founder, a large budget and months of work before you even know if it's worth pursuing, which is enough to put most people off starting at all. ### You don't know what it would actually cost Without a rough figure, it's hard to judge whether the idea is worth pursuing at all, so it sits untested rather than risking a conversation that might reveal it's unaffordable. ### You're not sure it's technically possible, or sensible, as you've imagined it Ideas often need shaping: some features matter far more than others, and some assumptions about how it should work don't survive contact with how customers would actually use it. ### Finding someone to build it feels like a minefield Horror stories about developers disappearing mid-project, or building the wrong thing entirely, make it hard to know who to trust with something you've been carrying around for a while. ## What fixing it looks like The right first step is almost never "build the whole thing." It's making the idea concrete enough to test, show people and price properly. [Idea shaping and a clickable prototype](/services/custom-apps) turns a rough concept into a clear plan and a working, clickable mock-up you can actually click through and show to potential customers, investors or partners, before committing to a full build. If the idea is really an internal need, like replacing a spreadsheet that's become the unofficial backbone of the business, an [internal tool or dashboard](/services/custom-apps) built specifically around your process is often the more useful next step than a public-facing app. From there, a proper build is scoped with a fixed price, informed by what the prototype revealed, rather than a guess made before anyone had seen it working. ## When it's worth getting help, plus what it typically costs If you've shaped the idea as far as you can on your own and the next step is making it real enough to show people or raise money against, that's exactly where a proper prototype earns its keep. Idea shaping and a clickable prototype starts from £750. An internal tool or dashboard, once the idea's been shaped, starts from £3,000, and a full custom app or portal build varies with scope and is priced after that stage. These are guide prices for typical projects; the fixed quote comes after a free 30-minute call. See [pricing](/pricing) for the full list. ## Related reading - [Off the shelf or custom software? An honest comparison](/guides/off-the-shelf-vs-custom-software) - [How much does a custom app cost for a small business?](/guides/custom-app-cost-uk) - [How to brief a software project (and get accurate quotes)](/guides/how-to-brief-a-software-project) - Example project: [a new venture going from app idea to clickable prototype](/examples/startup-mvp-prototype) - Example project: [a letting agent with a maintenance portal for tenants and landlords](/examples/letting-agent-maintenance-portal) - Particularly relevant for [property](/industries/property) and [professional services](/industries/professional-services) businesses considering their own custom tool. ## What you can do this week yourself - **Write the idea down in one paragraph**, as if explaining it to a stranger. If that's hard to do clearly, the idea likely needs more shaping before anyone can build it. - **List who the app is actually for**, specifically, not "everyone." A clear first user makes every later decision easier. - **Sketch the three or four screens that matter most**, even roughly on paper. Most ideas are simpler at their core than they feel in your head. - **Look at one or two existing apps that do something similar**, even loosely, and note what you'd keep and what you'd do differently. - **Decide what success looks like for a first version**, specifically, so you know what you're actually testing before you build anything. - **Talk the idea through with someone outside your own head**, a colleague, a friend, a potential customer, before spending anything on it. ## Frequently asked questions ### Do I need to know exactly what I want before talking to a developer? No. Part of the first stage is helping shape a rough idea into something specific and buildable. Arriving with a clear problem and a rough sense of who it's for is enough to start a useful conversation. ### How much does it cost to build an app for a small business? It varies enormously depending on scope, from a simple internal tool to a full customer-facing app with logins and payments. Our [guide to custom app costs](/guides/custom-app-cost-uk) gives a realistic breakdown, but a clickable prototype is usually the affordable first step that makes a proper estimate possible. ### What's the difference between a prototype and the real app? A prototype is a clickable mock-up that looks and feels like the real thing but isn't actually built to run or store data. It exists to test the idea and show people before committing to the cost of a full build. ### Should I build an app myself using no-code tools, or get a developer? No-code tools can work well for very simple ideas and are worth trying if you're comfortable experimenting. Anything with real complexity, multiple users, or data that needs to be reliable usually outgrows no-code tools quickly, at which point a properly built version makes more sense. ### How long does it take to go from idea to a working first version? Shaping the idea and building a clickable prototype typically takes one to three weeks. A full build after that varies hugely with scope, from a few weeks for a simple internal tool to several months for something like a customer portal.