Skip to main content

For service businesses

Build an internal tool from your spreadsheet.

To build an internal tool from a spreadsheet, attach the file to a Build chat in Kaer, say who uses it and what they need to do, and check the live preview it produces. You ask for changes in plain words and publish when it is right. Nobody on your team needs to write code.

Which spreadsheets should become tools?

The ones several people edit, and the ones that break when someone sorts a column.

  • The job tracker

    A board for the office and a phone-friendly view where each fitter sees only their own jobs.

  • The booking sheet

    A booking form for clients and a calendar view for you that flags double bookings.

  • The quote calculator

    A form that applies your rate card and minimums, so two people quoting the same job get the same number.

  • The stock list

    Stock in, stock out and a low-stock view, in place of a shared file with three versions.

  • The rota

    Who is on which job this week, with the clashes marked before anyone turns up.

How do you go from spreadsheet to working tool?

Describe the result, check the preview, then publish. Most of the work happens in one chat.

  1. 01Start a Build chat

    Switch the chat to Build and attach the file with the paperclip. Kaer reads .xlsx, .csv and .tsv.

  2. 02Describe the people

    Say who uses it and what they do. “A form for clients and a calendar view for us” works better than a list of tables.

  3. 03Check the preview

    Kaer builds it and shows a live Preview on a private address. Ask for changes in the chat until it is right.

  4. 04Publish it

    In Manage, open Publish, choose an address on kaer.dev and click Publish. A custom domain works if your domain is on Cloudflare.

When should you keep the spreadsheet?

When one person uses it and it works. A tool earns its place once several people edit the same file or a mistake costs you money.

  • One person, a simple listKeep the sheet

    A tool adds a running cost and solves nothing here.

  • Several people editingBuild a tool

    Forms stop people overwriting each other, and each person sees what they need.

  • Customers need to use itBuild a tool

    A form on its own address beats sharing a spreadsheet with people outside the business.

  • You already have engineersOpen a pull request

    An agent with GitHub access can open a pull request on your codebase for them to review.

What does it cost to keep a tool running?

A published app is billed by the hour while it runs. It sleeps after ten minutes unused, so a tool people dip into costs less than one kept open all day.

  • While it is running

    Billed by the hour. The usage rate card lists the current rate.

  • While nobody is using it

    It sleeps after ten minutes unused and wakes when someone opens it.

  • If you stop needing it

    Click Unpublish at any time.

Questions

Do I need a developer to turn a spreadsheet into an app?
No. You describe the tool and review the preview, and Kaer writes and hosts it. The files are there if you want to look at them.
Who can see the tool?
Nothing goes public until you click Publish, and you choose whether it shows in search results. If only your team should use it, say so in the brief and test the sign-in in Preview before you publish.
Will it stay linked to my spreadsheet?
Treat the file as the starting data. Once the tool is live, that is where people edit. If you need it to keep reading a live sheet, say so in the brief and test it in Preview.
Can I change the tool later?
Yes. Ask in the chat. Changes are previewed before they replace what is live.

Where to go next

Bring the spreadsheet you are tired of.

Starting is free and needs no card.