A tool for the way your business works.

Start with one job you keep doing by hand.

The most useful first tool is often a small one. Think of the spreadsheet you keep rearranging or the information you have to collect from three places before you can answer a simple question.

A workshop tracker could put bookings and available places on one screen. A project list could show what is waiting on a client. A stock tracker could help you see what needs reordering. Pick the job you understand well enough to recognize a useful result.

With Thumbs, you can describe that job to AI agents from your iPhone. Your invite sets up a cloud computer with the agents installed. You sign in with your supported AI subscription and work through the idea in a conversation.

Thumbs is in invite-only early access. You need an invitation and your own supported AI subscription to use this workflow.

Explain the day, before the screens.

Start with the process you already follow. What information comes in? What do you do with it? What do you need to see afterward? Use a real example, even if you change the names and numbers for the prototype.

For the pottery studio, the process might be: someone asks for two places in Saturday’s class, you add the booking, and the number of available places falls from eight to six. If they cancel, the places become available again.

That small story tells the builder more than a request for “a modern booking dashboard.” It also gives you a way to check whether the result works.

• Say who will use the tool. A private tool for you is a different project from a booking site customers use themselves.
• Name the information you need to enter and the result you want to see.
• Describe the ordinary exceptions, such as a cancellation or a workshop that is full.
• Say where the information lives today, and ask before connecting any existing service.

Give your team a small first version.

Ask for a version you can try with example information. You can learn a lot from entering a few bookings yourself, before adding integrations or extra screens.

Keep talking to your team if it asks a question. You know which detail matters to your business. You can also ask it to explain a choice in ordinary language before it goes ahead.

Try the whole journey.

Open the preview and do the job the tool is supposed to help with. Add something, find it again, change it, and check the result. Reload the page. See whether the information and totals behave the way you expect.

Ask someone else who does the job to try it, too. Notice where they pause, what they misunderstand, and whether they can recover from a mistake. These observations give you useful next changes.

For a bigger job, a Thumbs squad can have a separate agent review the work. Read its findings and compare them with what you saw in the preview.

Know where the information goes.

Before you rely on the tool day to day, ask your team to explain where it saves information, who can open it, and how you can back it up or export it. Those answers should make sense to you.

Your project files live on your Thumbs computer. A tool you build may use its own database or a service you connect, so ask about the actual setup rather than assuming that the preview explains it. If you use a hosted computer, its hosting provider’s storage terms also apply.

A useful first version should fit a real routine: open it, do the job, and come back later to find the result. If a part of that is unclear, ask your team to make it clearer.

Build on the parts that save you effort.

Use the tool on a small, familiar workflow and keep a note of the things you still do by hand. A filter, a better summary, or a simpler way to correct an entry may be more useful than a whole new feature.

You can send that next change in the same conversation. Your team and project are still on your computer, ready to pick it up.