Questions
The questions people ask before starting
Building an application without coding, code ownership, lead times, costs, AI reliability: direct answers to the most frequent questions, without the sales detour.
35 results
What is a business application?
A business application is software built around the things an activity manipulates: clients, projects, items, members, and the links between them. Everything has its record, its history and its status; filterable lists find anything; a dashboard aggregates it all into indicators. It differs from a website (an outward-facing showcase) and from a spreadsheet (data without shared structure): it is a team's internal working tool.
What if no software fits my business?
Start with the honest test: if a specialised, affordable, well-reviewed tool exists for your trade, take it, a good specialist beats a generic tool. The real problem starts when it doesn't exist, is oversized, or is priced for structures much bigger than yours. Three real paths remain: bending a generic tool (spreadsheet, CRM), assembling no-code, or describing your business and having the matching application generated, the only one of the three that produces a tool in your image AND whose code you own.
Can you build an application without knowing how to code?
Yes. Three paths now lead to a working application without writing code: no-code builders (visual assembly), conversational AIs that write code on demand, and deterministic generation, where AI produces a plan that programs turn into an application. The required skill is no longer programming: it is the ability to describe your need clearly.
Can AI build a reliable application?
Yes, provided you do not ask it to write the code freely. A model generating code on demand produces an unpredictable result that nobody audits and that any touch-up can break. Reliability comes from an architecture that confines AI to what it does well: understanding your business: and hands the code writing to deterministic programs, whose output is identical on every run.
What is the difference between no-code and low-code?
No-code lets you build an application entirely with the mouse, without writing or reading code: it targets non-developers. Low-code starts from the same visual base but expects the application to be extended with code: it targets technical teams that want to move faster. In both cases, the application stays executed by the platform: which is what separates them from a third approach, code generation.
How long does it take to build a business application?
It depends on the path: count several months for classic custom development, several days to several weeks to build the application yourself on a no-code platform, and a few minutes for a first AI-generated version from a description. In every case, the incompressible time is the same: clarifying what you actually need.
How much does a custom management application cost?
It depends on how it is made. Classic custom development runs to tens of thousands of euros and months of lead time; no-code platforms charge a subscription, often per user, that runs for as long as the tool lives; AI generation brings custom software down to a modest subscription: with Blueprint Maker, from €0 (Discovery) to €25/month (Pro) or €149/month (Max), with each generation's cost displayed before you launch.
How do you replace Excel with a real application?
In three steps: first, reread your workbook to extract its hidden structure: what things it tracks (the entities), how they connect (the relations), what states they go through (the statuses) and what totals you compute (the indicators); then pick a building path (no-code, development, AI generation); finally migrate gradually, with the application and the workbook coexisting for a few weeks. The classic starting signal: several people enter data, and versions diverge.
Who owns the code of a no-code application?
In most cases, nobody, because there is no code to own. A no-code application is a configuration executed by the vendor's platform: you own your data (usually exportable as CSV), but the logic, the screens and the execution stay with the vendor for as long as the subscription lasts. Only tools that generate real code and hand it over allow ownership in the full sense.
Can you self-host your generated application?
Yes: provided the generation tool hands you a real application, in standard technologies, able to run outside its platform. That is the case with Blueprint Maker: every generated application is a complete Next.js + Prisma project, exportable as a ZIP or pushed to your GitHub, which you deploy on the server or host of your choice. A dedicated URL is included if you would rather manage nothing.
Can you modify an AI-generated application?
Yes, in two complementary ways: regenerate the application from an enriched description: the no-code path, suited to structural changes: or take the source code and evolve it like any project, yourself or through a developer. The second path rests on an often-overlooked condition: the generated code must be standard and readable, not a tangle nobody dares touch.
Can you use your business app on mobile?
Yes. An application generated by Blueprint Maker is a web application deployed at its own address: it opens in the phone's browser, with nothing to install and no app store involved, and shows exactly the same data as on a desktop. You can add it to the home screen so it opens full-screen with its own icon. The one limit to know about: it needs a connection, there is no offline mode.
Is there a per-user cost on a generated application?
No. What is billed is generation: your plan sets what you can produce in a month, never how many people then use the application. It arrives with its own accounts and two roles (administrator and read-only), which you create from within the application. There is no seat counter to watch. The only real limit is hosting, not a licence.
Is the generated software a real application, or just a mockup?
It's a complete application, not a mockup: a real PostgreSQL database (via Prisma), API routes that create, read, update and delete data, authentication, and an interface that READS and WRITES to that database. Before delivery, every application goes through automated validation: it must compile, start as it would in production, and let a browser click through every section — not just “look like” it works.
Can I cancel my subscription at any time?
Yes. The Pro and Max plans are billed monthly, with no annual commitment to break. Cancellation is self-service from the billing settings, with no call to make or reason to justify, and takes effect at the end of the period already paid for: access does not stop midway through a paid month. The code of applications already generated remains exportable regardless of the subscription.
What to do if my business software is no longer maintained?
Three moves, in this order. Get your data out while the service still runs: contractual restitution usually covers it, and the right to data portability backs you up. Then secure operations for the length of the switch, because software that still runs is not the same as software that is safe. Finally, pick a replacement by asking the question you missed the first time: if this vendor stops too, what stays in my hands?
What is the difference between an ERP and a generated application?
An ERP is an integrated suite covering several company functions (accounting, HR, procurement, production) on a shared database, deployed by a specialised vendor, often long and costly to implement. Blueprint Maker generates ONE targeted application for ONE operational need you describe, in minutes and at a cost known in advance: it is not an ERP, it's the alternative to the fragile spreadsheet for the tracking no ERP covers well, or whose cost puts it out of reach.
Is the generated application GDPR compliant?
Two levels need distinguishing. Blueprint Maker, the vendor, processes your account data in line with the GDPR: hosting within the European Union (OVH, France), sub-processors bound by standard contractual clauses, a right to data portability. The GENERATED application, on the other hand, is a tool you operate: you become the data controller for the data YOUR users enter into it — the platform makes that role easier (EU hosting available, a database you own, no lock-in), it doesn't take it on for you.
Do I need to change software for e-invoicing?
Two things need separating. The CHANNEL your business-to-business invoices travel through is regulated: it goes via an accredited platform, and that is where compliance is decided. Your day-to-day business tool — scheduling, job sites, service calls, stock, members — is not covered by the reform and has no reason to be replaced because of it. An application generated by Blueprint Maker is not an accredited platform and does not become one: it holds your data and works out your amounts, while transmission stays with your platform or your accountant.
Can a generated application have multiple users?
Yes. Any described application that requires a login ships with real account management, not a single shared password: the admin can create further accounts, either able to edit or read-only, each with its own username. Accounts are created from the Settings screen, with a one-time temporary password the person changes on first sign-in.
Can I import my existing Excel data into the application?
Two things need separating. Your workbook's STRUCTURE, yes: attach the .xlsx or .csv file to your description and its columns and sheets are read, becoming fields and entities in the plan you approve before anything is built. Your ROWS, no: there is no universal import screen, the application ships with demo data, and history is brought over either by hand across the perimeter that actually matters, or in one go through the database — a standard PostgreSQL database that belongs to you. In the other direction, though, the exit is immediate: CSV export from every list, JSON export of every dataset.
What happens if the person who runs the tool leaves?
What disappears when someone leaves is almost never the data — the file stays — it's the RULES: the formulas nobody else can read, the unwritten colour code, the step done on the 5th of the month that was never noted anywhere. An application moves those rules out of one person's head: they are written in plain language in the plan you approve before anything is built, then in standard code any developer can read. What stays beyond a tool's reach are the reasons — why that discount, why this client is handled differently — and those are passed on by talking, before the departure.
Can a generated application connect to your other tools?
Partly, and the nuance matters. Every generated application exposes a full REST API — one family of routes per data type — but it is protected by the session cookie: there is no API key yet that would let another piece of software connect on its own. Without writing a line, you do get JSON and CSV export of every dataset, file import on measurement data, and direct database access if you host it yourself. And because the code is yours, adding an API key remains a standard piece of work.
Who maintains the application two years from now?
First, a reassuring and verifiable fact: a generated application pins its dependencies to exact versions — Next, React, Prisma and the rest are fixed to the precise number, not to a range. So it reinstalls identically two years from now and does not break on its own. What does need upkeep is three separate things: security patches for the libraries, the hosting, and your own business changes. While the application lives at the included URL, the first two cost you nothing; the day you host it yourself or alter its code, it becomes software like any other — and since the code is standard Next.js and Prisma that belongs to you, any developer can pick it up.
How do you get your team to actually use the tool?
This is the question that decides the tool's fate, and it is rarely settled on technical grounds. The failure mode is always the same: the team uses the new software AND their spreadsheet, the two drift apart, and within weeks only the spreadsheet is current. A generated application has one real advantage here — it carries YOUR vocabulary, because it is built from your own description rather than a vendor's, who sells the same product to thirty trades. You can also rename the menus afterwards, and give whoever needs it read-only access that is genuinely enforced server-side. What the tool does not do: it trains nobody, it has neither a built-in tutorial nor usage tracking, and it will not tell you who is actually using it.
What if I describe my needs badly?
This is the objection that stops most people from starting, and it rests on a false assumption: that your description would go straight to code with no way back. That isn't the sequence. Your description first produces a PLAN — the list of data, screens and screen types — which is shown to you and which you correct BEFORE a single line of code exists: rename an entity, fix a field name, add or remove a status value, even change what kind of screen something is. At that stage, getting it wrong costs nothing. After generation, changes are still possible by describing them in plain language, but that rebuilds and revalidates the application: a heavier move, not a tweak.
Does the application work without an internet connection?
No — and the catch is that it looks as though it does: the delivered app installs to a phone's home screen like a native application, yet it needs the network on every screen. It does not hide that from you: with no connection, a list says “Server unreachable” instead of showing up empty, and a form you were filling in stays open with your values in it. What it does not do is store your data on the device or queue your entries for later sending. If you work from an office, a workshop or a shop counter, you will never meet this limit; if you work in a dead zone, you will meet it on day one — and this page tells you how to factor that in before you buy.
Is my data backed up?
The question covers three, and they do not have the same answer. A deletion made inside the application can be undone: nothing is really erased, the row goes to a trash from which a button restores it. Your data comes out whenever you want, every list having its own export. But a deployed application's database is backed up by NO automatic mechanism in the product — there is no backup command anywhere in the deployment chain, and it is the host's job to put one in place. Put plainly: one click too many fixes itself, a lost database does not. This page says exactly where the line runs, so you can ask the right questions before putting real data in.
What does the AI see of my data?
Two moments have to be separated, and the word “data” blurs them. During generation, what you WRITE — your description, and the text of the files you attach — is transmitted to a model provider in order to produce the specification and the code; the providers are named in the privacy policy. Afterwards, once the application is running, nothing leaves: the delivered code carries no artificial-intelligence client among its dependencies, and the configuration file written on the server holds no API key. Which means your customers, your service calls, your members — everything you will enter later — structurally cannot reach a model. The only material that goes out is what you wrote to describe your need.
Can I build an application for a client and hand it over?
Yes. The terms assign the rights to the generated code — on every plan, the free one included — and explicitly allow you to use, modify, host, distribute, commercialise, resell it or publish it on your own site. Three caveats nevertheless change what you really deliver, and it is better to know them before signing: the assignment guarantees NO exclusivity, the free plan grants Blueprint a licence over the applications it produces in return, and the bundled open-source components require their licence notices to be kept. What remains off-limits lies elsewhere: reselling access to the Blueprint service itself. This page states precisely where those boundaries run. It describes a contract, not legal advice.
Does the application send emails or automatic reminders?
No. An application generated here sends no email, no SMS and no push notification — and that is verifiable in the package you receive: not one of its declared dependencies is a messaging client, and the temporary password of a newly created account is shown ONCE on screen rather than mailed out. What it does instead is different, and often enough: it puts what is due in front of you the moment you open it — an overdue banner at the top of the lists concerned, a bell and a notifications page, a calendar view. And for the reminder that actually rings, it hands over to your own calendar: an “Add to calendar” button passes the deadline to your phone. If automatic sending is essential to you, the application's code is yours and a developer can add it — this page says what that involves.
Can I remove what I don't need before the application is built?
Yes, and it is a step of its own in the journey. Between the moment you describe your activity and the moment the application is built, a plan screen shows you what is about to be produced: the views, the data entities, the indicators, the values of your choice lists. Everything there can be changed — added, renamed, reordered, hidden, deleted — and nothing is built until you approve it. On top of that comes a point people often discover too late elsewhere: the size of the application is DERIVED from your description, it does not come from a catalogue of features to tick. This page states exactly what can be cut, at what moment, and what that does not solve.
Is the generated application accessible to people with disabilities?
Partly, and the honest answer comes in three parts. It is NOT WCAG-certified and has not been audited by a third party: no page on this site will tell you otherwise. Several foundations are nonetheless there by construction, because the interface is written by a deterministic program rather than redrawn each time — visible keyboard focus, reduced motion if your system asks for it, real forms, no native dialog boxes. At every generation, the accessibility tree of each screen is recorded and published in a report. What is missing is named below rather than left unsaid. And because the code belongs to you, an accessibility fix is ordinary work, not a request filed with a vendor.
Can I print a document from my application?
Yes, and with nothing to install. Every generated application ships with a print stylesheet: Ctrl+P — or “Save as PDF” — produces an A4 page stripped of the navigation, in black on white whatever theme is showing on screen. The summary statement goes further: it carries a deterministic “Print” button, its colour flats are faithfully reproduced, and its page breaks never cut an amount row in two. What you should know, on the other hand: the PDF is produced by the browser, not by a bundled library — so there is no invoice template on your letterhead, and no automatic emailing. This page states exactly what comes out of the printer, and what does not.
Can I manage several sites in a single application?
Yes. A second workshop, a second shop, several job sites: the site is DATA you describe at generation time, not a software edition to buy. Each record is attached to its own, lists filter, indicators are computed over what you have scoped, and no pricing line depends on the number of sites. Two limits are worth knowing before you start, and they matter: there is no GLOBAL site selector that switches the whole application at once, and accounts carry no per-site restriction — an account that can read, reads everything. This page states what works, which shape to choose for your sites, and what would take development.