A prototype 7 days after the audit call. Pay only if you like it.

Monday morning, and the spreadsheet is already open.

It may be an Excel file or a sheet online. It holds the orders, the jobs or the crew schedule, and everyone edits it.

By nine, a question reaches your desk. "Where's that order at?"

You find the row, and the status cell is blank. So you phone the person who should know.

Tuesday, a delivery date has moved since yesterday. "Who changed this?" The room goes quiet, and the person who knows is out on a job.

Wednesday, an order goes into the sheet. Then someone types it again, into accounting or into an email. "We type the same thing in twice," they tell you.

Thursday, the planner scrolls past every column to find this week's jobs. Your own notes sit in the same file, open to the whole team. "Everyone sees everything."

Friday, you want the week in one view before you go home. You catch yourself thinking: "I can't see where everything stands without asking around." So you ask around again: a call, a message, a walk across the floor.

By now the status of the whole company lives in your head and on your phone. When you are away, the questions wait for you.

The sheet still works well enough, so the fix waits for next week

Nothing has broken badly enough to stop the week. Customers still get their orders.

The fix waits. It needs your signature and a slice of your week, and there is always a customer who needs a call back.

You may have looked at systems already and come away saying: "We've outgrown the spreadsheet, but every system we look at wants us to change how we work, or charges for every user."

Three fears keep the decision on hold:

• Moving means your data leaves the sheet.
• A vendor could lock you in.
• If a tool breaks or loses data, your team is left alone with it.

Admin work now sets how fast the business can grow

Count the hours that go into chasing, retyping and asking around. That is the day-to-day admin work, and it keeps the business from growing.

More orders would mean more rows to check, more calls and more typing. The company stays the size the sheet can carry.

Skip ahead to what you get

1. the people who chase status in the sheet
2. each person's weekly hours spent asking around and retyping
3. your working weeks a year
4. what an hour of their time costs

Multiply them for the sheet's yearly cost. You give them on the audit call. They stay in the call notes.

Outgrowing the sheet means the business grew.

Keeping the spreadsheet as it is. It still works well enough, so it never becomes the priority of the week. The chasing carries on.

Off-the-shelf industry software or an ERP. The business has to change how it works to fit the tool. Many also charge for every user.

A developer or an agency. The project feels open-ended, with no fixed price and nothing to say the result will fit.

A no-code app builder. These tools turn Excel into a web app, and someone on your side has to build it. Nobody in your company builds software. Any real problem or lost data lands on your team alone.

Excel or VBA work inside the sheet. The sheet stays one file that everyone edits, so the chasing and "Who changed this?" stay. People in the same file still get in each other's way with filters and hidden columns.

We start from the columns your team already fills in. Your prototype is built from your own sheet.

We build the app. On the audit call we put what we build in writing, and the prices are further down this page.

Our method is The Column-First Build. It starts from the row of column headers at the top of your shared sheet. They name what your team tracks, in its own words.

We build the app around those columns. Your team keeps its columns and its way of working, and nobody on your side builds anything. In the finished app, one screen shows where every order or job stands.

Three things make 7 days enough for the prototype:

• The prototype is built from the columns your team uses, which we read before the audit call.
• The scope is a short list, written down on the audit call, and the prototype stays inside it.
• The prototype runs on sample rows, so none of your data has to move before day 7.

The four steps below take your headers to a prototype of your sheet on day 7.

1. 1Your column headers
2. 2The audit call
3. 3Days 1 to 6
4. 4Day 7

1. You send your column headers with the form

The form on this page has two short steps. In the second, you paste the header row of your sheet, with nothing under it. A header row is just the names of your sheet's columns.

We read them before the audit call, so the call starts from your own columns. The prototype later runs on sample rows we make from your headers, so your team types no test data. Your real sheet stays where it is until the finished app.

2. On the audit call, we talk through what you need and write the list

The 30-minute audit call opens with how your sheet runs today and what you need from it.

Next we write the list together. It holds 3 to 5 lines, each a screen, a role and an action. The cap is 5 screens and 2 roles.

We bring The Sector Starter List: draft lines for your kind of business, so you edit lines that already fit. The list, in writing, is the prototype's scope.

You also name the one connection you want next, to accounting, email or CRM. On the same audit call we agree what the finished app must do, and we book the day-7 walkthrough.

3. Days 1 to 6: each role's screen takes shape, one link per change

Day 1 begins once the list is agreed and your column headers are with us. Each role on your list gets a screen of its own, with that role's actions from the list.

The planner might get this week's jobs, and the owner the whole picture. In the finished app, each person logs in to their own screen.

The What-Connects-Next Screen shows the connection you named, greyed out in your prototype, so you see the next step before you decide.

A private progress link arrives with every change, so you watch the prototype take shape before day 7. Open it when it suits you, and comment when you like. There is nothing to install.

4. Day 7: you go through the prototype and say yes or no

The walkthrough on day 7 is a 30-minute meeting. You open each screen yourself and tell us in that meeting whether you like it. Nothing is due before then.

You judge a prototype of your app, made from your own columns and filled with sample rows. It shows the screens, roles and actions on your written list.

At the same meeting you get the build plan. It puts the finished app in writing, as we agreed it on the audit call, with your connection at the top. You find its price further down, under "What it costs".

Our founder has more than ten years of experience building software in banking, travel, telecom, health and online education.

Our biggest case study is Aargauische Kantonalbank, where we helped build internal applications for the bank's employees, as part of the digitalisation of its processes.

A hair clinic in Thessaloniki ran on software built in 2000. The clinic feared its software would stop working.

We built the clinic a prototype first, then a custom CRM that still runs today. We have shipped changes to it every week since July 2026. It runs on the platform your finished app runs on.

Your project follows the same order. You judge the prototype and decide before the app is built.

• Day 0, the audit call: what you need, talked through; the written list; the walkthrough booked.
• Within 48 hours: the earliest progress link.
• Days 3 to 5: the rest of the list, one link per change.
• Day 7: the walkthrough, your decision and the build plan.
• About three weeks after you go ahead: the finished app. You decide again; on a yes, choose Care, Care Plus, or the code once the app is paid.
• 30 days after the walkthrough: the prototype's hosting ends.

Peak Code Consulting is a GmbH registered in Switzerland, and we work in German and English. You talk to the engineer who builds your app, from the audit call to delivery.

The 7 days go to screens, roles and actions. Formulas, macros, logins, your real data and the connections to accounting, email or CRM all wait.

They come with the finished app as agreed on the audit call, at its one price. Leaving them out makes 7 days enough.

With no spreadsheet beside your industry software or ERP, this offer is the wrong fit.

Set each price beside the yearly cost your four numbers give.

We take on 3 prototypes a month, so each one gets our full attention. Today's prices are where we start, and they will rise as demand grows.

At delivery you choose Care or Care Plus, billed monthly. Or, once the app is paid, take its code and written documentation and host it yourself.

Both plans run your app on several servers on our AWS platform. If one fails, your app stays online.

We test each change on a copy before it goes live. Backups run automatically, and we test that they restore.

We monitor the app around the clock, apply security updates and keep its software current. Bug fixes use none of your hours.

Work beyond a plan's hours is billed per hour.

The 7-Day Sheet-to-App Prototype starts with a 30-minute audit call, where we talk through what you need. The Column-First Build then makes your prototype from your team's column headers.

7 days after the audit call, you go through a prototype of your app in a 30-minute walkthrough.

Pay only if you like it, on day 7 and again at delivery. Each stage's price is in "What it costs" above.

Next: the form below. We reply by email with a time for the audit call.