DeutschEnglish
Get in touch

Tailor-made web apps for SMEs

Do you pay every month for customer-related software? Have your own app built. You pay for the build once, and it runs in your account.

Talk about your case

Who this is for

Your own app suits SMEs that want to cut running costs and would rather have something built once. Perhaps you recognise yourself in one of these situations. If a tool that already exists solves your case more cheaply, we will tell you.

  • The subscription keeps getting more expensive.

    Your CRM, for example. With your own app, you pay for the build once. After that, you pay the provider directly for your own accounts.

  • Every new person on the team costs another licence.

    The price of the build depends on what the app has to do, not on the number of people.

  • With a subscription, you pay for many features and need only a few.

    Your own app does exactly what your team needs. We do not build what nobody uses.

  • The tool does not fit your workflow.

    Everyone on the team works around the tool. Your own app follows your workflow.

Your benefits

Pay once instead of every month

You pay for the build once. The only regular payment to us is for ongoing support, if you want it. You pay the provider directly for hosting.

Only the features you need

You decide in the concept what the app has to do. You pay nothing for features that nobody at your company uses.

The app and your data stay with you

The app runs in your own Cloudflare account, not in ours. Its data is stored there too.

90 days of fixes

If you come across a build defect after acceptance, we fix it at no extra cost for 90 days. This applies to every part that nobody has changed since acceptance.

What already exists

We have never yet taken a client through the whole process on this page. That is why there is no case study here.

What we do have are apps that we built for ourselves and for client projects. Most of them run in our own Cloudflare account today. Five measurements from them.

  1. 19 August 2026

    The CRM goes live

    Today we keep companies, people, quotes and logged time in it. On the first day, our own attack test went after every layer of protection. 47 of 47 attempts came to nothing.

  2. 31 August 2026

    The Lead Engine goes live

    Our attack test checked twelve layers of protection. 73 of 73 attempts came to nothing. One layer checks that there is no way of sending anything.

  3. 31 August 2026

    Login without a password

    Four of our apps share one login by one-time code. Tested against the live apps, it blocked 63 of 63 attacks on each.

  4. 17 September 2026

    A counter that finds the clicks

    194 paid clicks led to two of our pages. There, our visit counter recorded 197 hits and Google Analytics 29. Counted from 6 to 16 September 2026.

  5. 28 and 30 September 2026

    Form and calculator, measured end to end

    For a landscape gardening business, one test enquiry each ran through the whole chain, all the way into the business’s enquiry table. Since 30 September, the calculator also records which channel an enquiry came through.

One-off

payment for the build, not every month

CHF 0

for your accounts while we build

90 days

in which we fix build defects in unchanged parts at no extra cost

Optional

ongoing support after the handover

All measurements in this section are our own. The apps were running in our account at the time, not in an account belonging to a client.

How it works

You get to your app in five steps. We only set up the accounts in your name at handover. Until then, they cost you nothing.

1

In the concept, you decide what the app has to do.

To do this, we work out the task, scope, data, integrations and data protection with you. Only then is the price set. That way, you can compare before you decide. The concept belongs to you, even if you do not have the app built afterwards. The concept is included in the guide price.

2

We build and test on our side.

We develop the app with our AI team, which works with Claude Code. Testing uses test data only. Before anything goes to you, a human on our team checks it.

3

Only now are your accounts created.

Only when everything is ready for handover do we set up a Cloudflare account with you. If your app uses AI, an API key in your name is added. Everything is billed to you. That way, these accounts cost you nothing during the build. The login details stay with you. We never see or store them.

4

Now you get your app.

It comes with its tests and an operating guide.

5

We finish the setup on your side. Then you drive.

For this, you invite us into your account. We set up the app there and check it with you. We put the acceptance on record. After that, you drive yourself, and our access ends, unless you book ongoing support.

We build the car. You are in the driving seat.

You get the engine and the car from us, fully built and checked. You decide where you drive it and how fast. We have no influence on that.

That is why we promise you one thing

The solution works.

We never promise a result such as enquiries, contracts or revenue.

digital M.onster with a spanner in front of a small car

How we put this in writing

  • At acceptance, the app does what the quote says. That is on record.
  • Whatever we built wrongly, we fix at no extra cost for 90 days. This applies to every part that nobody has changed since acceptance.
  • If a provider such as Meta, Google or Bexio changes its interface, that is not a build defect.
  • After acceptance, we only look after keeping the app running if you book ongoing support.

We check what we deliver. What you do with it afterwards is up to you.

What we have already built

This is what your app could look like. The examples come from our own business and from client projects. Each one says what the app does, what there is evidence for and what it would be at your company. What it has achieved is not listed. We do not name any of our clients.

Our AI team built them. How that works day to day is described in the post Building an AI team with Claude Code (in German).

Size: Large

Our own CRM

Built for ourselves. We call it M.appe.

What it does

It keeps companies, people and quotes in one place. It also has time tracking on your mobile, email history and calendar, permissions per person and a login without a password.

Evidence

It has been running at our company since 19 August 2026. On the first day, it blocked 47 of 47 attacks in our attack test.

No evidence yet

Use in a company like yours. Some parts are still missing for that today, such as login with email addresses from other companies, and an export.

At your company

You would get a CRM of your own in your account, with the features your company needs. There is no access to ours.

Good to know

There is no AI in the CRM itself. For us, AI is the way we build it. If a standard CRM solves your case more cheaply, we will tell you.

Open demo Our own CRM, sample data

Rebuilt with made-up data.

Open in new tab

Size: Large

As a bundle: large. A single app on its own: medium.

The sales apps

Built for an agency. Run in its own account.

What it does

Three apps work on one shared data set. The first finds companies where something is happening right now, such as a change at the top or a merger. Each day, at most ten new ones are added, the most important first.

The second prepares an email draft for each company, with two matching case examples attached. A human has to send it. The third shows which initiatives support the sales effort and what the figures say about them.

In operation, there is one more area that the demo does not show: public tenders. Each entry gets a decision. Everything sits behind one login, with roles for the team.

Evidence

The apps run in the agency’s own Cloudflare account. They are fed by a Claude Code setup at the agency.

The handover includes a package with code, instructions, interfaces and test scripts, as of 9 October 2026. It can be used to set the apps up again in another account.

The demo shows the real interfaces, just with made-up data.

No evidence yet

A contract that came about through the apps.

At your company

They run in your account, with your triggers, your case examples and your signature. Nothing goes out unless someone at your company checks it and sends it themselves.

Open demo The sales apps, sample data. The real interfaces with made-up data. Opens in a new tab.

Size: Medium

The Lead Engine

Built for our own prospecting.

What it does

The Lead Engine finds companies and prepares first contacts. You have to do the sending yourself. We do not promise contracts.

Every day, it looks for businesses in a set area and measures their websites from the outside. For each match, it lays out the finding and an email draft. It has no way of sending anything, and that is deliberate.

Evidence

It has been running since 31 August 2026. Our attack test checked twelve layers of protection, and 73 of 73 attempts came to nothing.

No evidence yet

A contract that came about through the Lead Engine. Even before it, cold prospecting by email did not bring us any clients. None of the contracts we have won came from a prospecting email, counted on 21 August 2026.

At your company

It runs in your account and searches only for you. Who you write to and how is your responsibility.

Open demo The Lead Engine, sample data

Rebuilt with made-up data.

Open in new tab

Size: Small

Company Visitors

Built for us, on digitalm.ch.

What it does

It identifies which company visited your website and which pages it looked at. It does not identify people. With very small companies, the company name can still point to a person. Once a week, an email arrives with the companies it identified.

Evidence

It runs on our site with real visits. It only starts after consent.

No evidence yet

How many visits it can match to a company. We have not measured that on our site. We do not know whether an identified visit has ever led to a contract.

At your company

By default, it only starts after consent. With it, you get the list of what it stores and for how long.

From a mistake of our own

Our weekly email once said that no personal data was stored. The company, the location and every page visited were stored. That is why this list comes with every app.

Open demo Company Visitors, sample data

Rebuilt with made-up data.

Open in new tab

More small apps

Calculator with quote request

A calculator on the website of a landscape gardening business. It works out garden maintenance as a subscription or as a one-off. The enquiry lands in the business’s enquiry table, together with the channel it came through.

Evidence:
On 30 September 2026, a test enquiry ran through the whole chain, channel included.
No evidence yet:
Today it runs in our account, not in the business’s.

Form bridge with source

It picks up the enquiries from an existing contact form. It writes them into a table and sends an email. It also records which channel the enquiry came through, as a single word. It never stores identifiers from ad links.

Evidence:
On 28 September 2026, a test enquiry ran through every link in the chain.
No evidence yet:
In two rare cases, it still reports success without sending.

Visit counter

It counts visits without cookies. It does not store an IP address, only shortened details, such as the domain someone came from and the device type.

Evidence:
The measurement from 17 September 2026 further up.
No evidence yet:
Use with clients.

Budget calculator

From revenue and industry, it calculates a recommendation for your marketing budget and sends it by email. It is publicly available on our site.

Evidence:
It runs on digitalm.ch.

Email gate before a download

It asks for the email address before a download. It checks the spam protection, adds the address to a list and then releases the download.

Evidence:
We use it in front of our AI Setup Guide.

Approval preview

It shows a page before it is published. Whoever is meant to look at it needs no account, only a code by email. Without permission, the page cannot be published at all.

Evidence:
It has been running at our company since 1 September 2026. Without permission, the build stops, checked on the same day.

Integrations for your agent

Small servers through which a Claude agent works with tools such as Bexio, Brevo or Google Ads. That way, it calculates with real numbers instead of guesses. The technical term for this is MCP server.

Evidence:
Our own AI team works with them.
No evidence yet:
Such an integration for a client.

Check first, then build

Would a tool that already exists do the job?

An initial consultation, 30 minutes, free of charge. Tell us what you pay for every month today and what you are missing. We will tell you whether you need your own app and what size it would be.

Book a consultation

At the end, you have an assessment, not a quote.

What it costs: three sizes

What your app costs depends on its size and on what it has to do. The amounts below are guide prices. We build every app for your company and its needs. That is why we assess every enquiry individually and give you a quote of your own. The price in it can differ from the guide price.

Small

Example: Company Visitors

CHF 3’000

Guide price

  • One task
  • One view or one report
  • At most one integration

Medium

Example: Lead Engine

CHF 6’000

Guide price

  • A login
  • Its own database
  • Two to three integrations

Large

Example: CRM

CHF 15’000+

Guide price

  • Many integrations
  • Permissions per person
  • A large amount of data
  • Migration from the old system

You get the quote after the concept. It covers testing, review, handover, completion on your side and a check after two weeks.

You pay for the build once. Compare that with what you pay for software every month today.

You pay the provider directly for your accounts, not through us. Ongoing support after the handover is an optional add-on.

We build one project at a time.

What you bring

You do not need any of this for the build. We set up the account with you once the app is finished.

Your own Cloudflare account or an alternative

This is where the app runs. We build on Cloudflare. If you want a different platform, we check in the concept whether the app runs there and what that costs. That is also where we clarify whether a free plan is enough.

A person who works with it

Someone at your company uses the app and is our contact person.

  • Depending on the app, another account is added, for example for sending login codes or for AI.

Where your data is stored

With a software subscription, your data sits in the provider’s system. With your own app, it sits in your own account.

  • The app and its data sit in your Cloudflare account.

    We keep no copy of your data after the handover.

  • Until handover, we only work with test data.

    Before we touch a real record, for example when migrating data, we sign a data processing agreement.

  • We decide where the database is located when we create it.

    This cannot be changed later. We create it in the EU. Cloudflare does not offer a Switzerland-only option.

  • If your app uses AI, that runs through your own contract with Anthropic.

    Anthropic processes data worldwide or in the US and stores it in the US. If you do not want that, use Claude through Amazon Web Services with a European profile. We include a note on this with the handover. As of October 2026.

  • Whether an app uses AI is set out in the concept.

    Apps without AI do not call a language model and run without Claude.

  • With every app, you get the list of what it stores and for how long.

    What goes into your privacy policy is written by your lawyer. We provide the basis, not the text.

  • If an app is to hold particularly sensitive data, such as health data, we clarify this separately before the concept.

After the handover

A car needs a service now and then. You decide whether we do it. Without ongoing support, you have no running costs with us.

Optional

Ongoing support

CHF 840

Guide price per month

  • Cancellable monthly.
  • We watch the alerts and fix whatever fails.
  • We renew access before it expires.
  • If a provider changes its interface, we update the app to match.
  • We install security updates.
  • Every change waits for your approval. There are no silent updates.
  • Once a month, you get a short report.

Response time: 1 working day

Without ongoing support, you drive yourself. Our access then ends with acceptance.

What we do not build, and when you do not need your own app

What we do not build

We only build customer-related apps. They help you to:

  • win customers
  • capture enquiries
  • look after contacts
  • measure what gets through

We do not build accounting, ERP or shops. We also do not sell you what an AI tool can do on its own.

When you do not need your own app

Sometimes a subscription is the better choice.

  • When a tool that already exists solves your case more cheaply. We will tell you, and if you like, we will set it up for you, see Marketing Automation.
  • When you want to buy a result, not a tool.
  • When nobody at your company will work with the app.
  • When you only need the tool for a short time.

Guide prices from around CHF 3’000, paid once

We assess every enquiry individually. The quote comes after the concept. You pay the provider directly for your accounts. The initial consultation is free.

Book 30 minutes