Guide
A small internal tool without code, shared safely
For this guide and its prompts we recommend:
Offers checked 21 Oct 2026
You can now build a team tool without code.
One small working tool for your team (for example a stock counter or price calculator), shared with the right people only.
What you need
- One small job your team does by hand today
- Any AI chat assistant and a shared document for the spec
- A spreadsheet and a no-code app builder, or an AI app builder that works from plain words
- Test data with no customer personal data
- Typeform for test feedback
Recommended AI tools
TypeformAnswers from real people instead of guessesFree plan
Steps
Describe the tool on one page
Write who uses it, what they enter, what it shows and what it must never do. One job only. Ask a chat assistant to turn your notes into a short spec with screens and fields.
WeakAn app for the shop.
BetterA stock counter for two staff. They pick a product, enter the count, and see the difference from last week. It must not show purchase prices.
Build it on a spreadsheet
Put the data in a spreadsheet, one row per item, and point a no-code app builder at it. Build only the screens in the spec. Use made-up test data, never real customer details.
Or describe it in plain words
If a sheet does not fit, describe the tool to an AI app builder that works from plain words, one screen at a time. Test each change before you ask for the next.
Test it and log what breaks
Ask two people to use it for a real task with test data and log every problem in a sheet: what they did, what happened, what they expected.
ExampleTester, step, what happened, what was expected, fixed yes or no.
Share it with the right people only
Before sharing, check the access settings: who can open it, who can edit, whether the link works for anyone. Invite named people only and remove access when someone leaves.
The full instruction
Copy it into any AI chat assistant and change only the first line.
Change only this line: JOB = [weekly stock count for two shops] You help me describe an internal tool for my team that does my JOB, before I build it without code. First ask me, one question at a time: who uses it (roles, how many people), what they enter, what it shows, and what it must never show or do (for example purchase prices, customer details). Write a one-page spec: 1. Screens, at most 3, with their fields. 2. The data table it needs: columns and one made-up sample row. 3. Who can view and who can edit. 4. A test plan of 5 steps with test data only. After my answers, start with the screens.
What you end up with
One small tool that does one job, tested with test data, shared only with named people and with a log of what was fixed.
Common mistakes
- Building several features before the first one works.
- Using real customer data in a prototype.
- Sharing a link that anyone with the link can open.
Processes that need more than one tool
Each process below uses several tools, each for the job it does best. Any AI chat assistant works where one is named.
Describe the tool
Tools, in order: any AI chat assistant → a shared document
- Answer the chat assistant's questions about the job, the users and what the tool must never do.
- Paste the finished spec into a shared document and agree it with the people who will use it.
The prompt for this process
Interview me about a small internal tool before I build it without code. Ask one question at a time and wait for my answer. The job: [e.g. weekly stock count] Cover: who uses it, what they enter, what it shows, what it must never show, who can edit. After at most six questions, write a spec with at most 3 screens, their fields, the data columns and one made-up sample row. Start with your first question.
Build it on a sheet
Tools, in order: a spreadsheet → a no-code app builder
- Set up the data in a spreadsheet, one row per item, with made-up test data only.
- Point a no-code app builder at the sheet and build only the screens in the spec.
The prompt for this process
Help me build my small tool on a spreadsheet with a no-code app builder. My spec: [paste] My sheet columns: [paste] Tell me which columns each screen needs, which columns must be hidden from users, which fields should be read-only and five made-up test rows I can use. Point out anything in the spec that a sheet-based tool cannot do well. Start with the screens.
Or describe it in plain words
Tools, in order: an AI app builder that works from plain words → any AI chat assistant
- Describe the first screen to an AI app builder that works from plain words and test it.
- Ask the chat assistant to turn each problem you find into one short change request, one change at a time.
The prompt for this process
Turn my spec into change requests for an AI app builder that works from plain words, one at a time. My spec: [paste] What the builder made so far: [describe] What is wrong: [describe] Write the next single change request in at most 60 words: what to change, what must stay the same, and how I will test it. No customer data, test data only. Start with the next change request.
Share it safely
Tools, in order: a no-code app builder → Typeform → a spreadsheet
- Check the access settings in the app builder: named people only, view or edit per role, no public link.
- Collect test feedback with a short Typeform and log each problem in a test sheet until it is fixed.
The prompt for this process
Help me share my small internal tool safely and collect test feedback. Who needs it: [names or roles, view or edit] What it shows: [describe] Write an access checklist of at most 8 points (named people only, roles, no public link, remove access when someone leaves). Then write a Typeform of at most 4 questions for testers: what they did, what happened, what they expected, anything that felt unsafe. Start with the checklist.
For this result we recommend these tools
This guide describes a result. These tools are one way to get there faster. Whether one pays for itself depends on your work, and we promise no result.
Typeform
An online form and survey builder with AI form creation.
From €25 per month (Basic, billed yearly; 100 responses a month) (source, checked 2026-10-16)
Typeform builds conversational online forms and surveys that show one question at a time. In this guide it is used in “Share it safely”. It is used for quizzes, feedback and lead forms, and its logic skips questions that do not apply, so more people finish.
Free plan · 14-day free trial (source, checked 21 Oct 2026)
We recommend a specialised tool for each process rather than one tool that does everything. Tools that try to do everything rarely do any one job really well, because no single function gets perfected. It is the same in life, in business and in relationships: spread your attention over ten places and nothing gets done properly.
Forward, without brakes
Now that the Kailiniai Heroes exist, you can have your own. Create one hero or several, and use them for goals that used to need a whole team or a big budget.
