What you keep

What you get to keep.

There are four ways to get the screen your business is asking for: an AI builder that knows the web but not M3, a low code platform beside M3, a development project, or Loupe Code. They differ most in what you are left holding afterwards.

Try Loupe Book a demo

Three things you keep

No licence on the result

You licence Loupe to build with. What Loupe Code builds is a standard H5 app, and running it costs nothing extra. Roll it out to ten people or a thousand, in every environment you have, and the price is the same.

It runs in M3

Not beside M3 on someone else's platform. Inside it, in H5, using your M3 sign in, your M3 roles and your real transactions. There is no second system for IT to host and no second login for users.

The code is yours

Readable source you can open, review and sync to your own git repository. If you ever stop paying us, everything you built keeps running, and your developers can pick it up from there.

Side by side

Scroll the table sideways to see the rest.

How Loupe Code compares with generic AI builders, low code platforms and a custom development project
What you end up with	Loupe CodeBuilt in Loupe, runs in M3	Generic AI buildersPrompt to web app, any industry	Low code platformsDrag, drop, connect, publish	A development projectConsultants, specs, sprints
No licence to run what you builtThe result is a plain H5 app	Yes	No. A plan per app	No. Runtime licence per user	Yes
Cost stays flat as more people use itRolling out is free	Yes	No	No	Yes
You own the source codeReadable, and yours to keep	Yes	Some of it, some of the time	No. There is no code to own	Whatever the contract says
Syncs to your own git repositoryYour repo, your history	Yes	Sometimes, on higher plans	No	Yes
Runs inside M3 H5Where your users already are	Yes	No. A separate web app	No. A portal beside M3	Yes
Uses M3 sign in and M3 rolesNo second user directory	Yes	No	After an integration project	If it was built that way
Built from your real M3Your transactions, fields, custom fields	Yes	No. It guesses at M3	Whatever you mapped by hand	Yes
No integration to build firstConnected to your M3 before the first sentence	Yes	No	No	The integration is the project
Change it by describing the changeNo change request, no backlog	Yes	Yes	Someone edits the model	Back into the backlog
Every user gets their M3 languageAdded with a click	Yes	No	Translate every label by hand	Costed as extra scope
Built against your live environmentReal data, never a sandbox	Yes	No. Invented sample data	A copy someone loaded	Yes
Time to a screen your team can open	Hours	Hours, but not in M3	Weeks	Months

The three columns on the right describe how each category usually works, not any one product. Terms vary, so check yours. Ours is simple: one licence for Loupe, usage for what you build with Code, and nothing to pay to run what you built.

Instead of an app builder on an integration platform

A platform beside M3 gives you a builder, a runtime, and a bill that grows with the number of people using what you built. The builder is the part you see. Under it sits an integration to your M3 that somebody has to build by hand first, usually a consultant, usually by the day, and “no code, just conversation” begins once that is done. The app lives there, not in M3, so it needs its own sign in, its own connection to your transactions, and its own place in your architecture diagram. When you leave, the apps do not come with you, because there is no code to take.

Loupe Code produces the same kind of H5 app a developer would have written. It runs inside M3, on M3 sign in and M3 roles, and the price for running it is nothing. Roll it out to the whole warehouse and the invoice does not change.

Instead of a generic AI builder

Prompt to app tools are genuinely impressive and they know nothing about your ERP. Point one at M3 and it invents field names, guesses at transactions, and hands you a web app hosted somewhere else that has to be wired into your environment before it can do anything real.

Loupe Code is connected to your environments before you type the first sentence. It reads your programs, transactions and fields, including the custom fields your business added, and it writes to the conventions H5 actually follows. More on why that matters.

Instead of a development project

A project gets you exactly what you specified, months later, at a price per day. It is the honest comparison for Loupe Code, because the output is the same kind of thing: real code, running in M3, owned by you. The difference is the loop. A sentence instead of a specification, an afternoon instead of a sprint, and a change made by describing it instead of queued behind the next release.

Consultants still matter for the hard problems. What they should not be spending their week on is the list a planner wanted sorted differently.

The part people check twice

You pay for Loupe to build with. What Loupe Code builds needs no licence of its own, because it is standard M3 extensibility: an H5 app, an H5 script, an XtendM3 extension. Install it in every environment you have. Give it to everyone who needs it. If you stop paying us, all of it keeps running, and the source is already in your git repository.

The questions people ask about that

Run it in your environment.

Bring an environment. We will show you what one sentence can build, and what you keep afterwards.

Try Loupe Book a demo