Your first internal tool
Build the small app that gets your team unstuck — without becoming an engineer.
What you'll have at the end
A working internal tool your team can actually use this week. Lives somewhere safe, only the right people see it, and you understand every piece well enough to change it.
01
Who this is for
- Operators tired of the same shared spreadsheet
- Small-team leaders who want one button instead of three steps
- First-time builders who haven't shipped anything yet
02
How to frame the idea
Start with the smallest annoying thing your team does every week. Don't build a 'system' — build a button. The button is small enough that you can describe it in one sentence and brave enough that, if it broke, you'd know exactly what to fix.
03
What people actually build
Request intake form
Replace the email-back-and-forth for new project requests. Form in, table out, one notification to the right person.
Inventory check-in/out
Who has the demo laptop right now. One screen, one history table, one Slack ping.
Vendor approval queue
Marketing submits a new vendor. Finance approves. Status changes. No more chasing.
04
Tool choices, honestly
Lovable
You want to describe it in plain English and see the screen appear. Best for the first 80%.
Cursor / Windsurf
You're comfortable reading code and want to tighten the last 20% by hand.
Airtable / Notion
Honestly — if the answer is 'a fancy table for 3 people,' don't build an app. Use the table.
05
Prompts you can lift
Frame the build
Help me design the simplest possible internal tool that does ONE thing: <one sentence>. Tell me the screens, the data table, and the access rules. Don't add features I didn't ask for.
Lock down access
Add email/password authentication. Only let users with an @mycompany.com address see anything beyond the login page. Show me the exact rules so I can verify.
Hand it off
Write a one-page README for a non-technical teammate explaining what this app does, how to use it, and what to do if it breaks.
Save and reuse these prompts in PromptlyDo™ with your favorite AI.
- Install the PromptlyDo™ browser extension
- Sign in or create a free account
- Right-click any prompt above and save it to PromptlyDo™
06
What tends to break
- Building a system instead of a button. Scope creeps from 'submit request' to 'full PM tool' in three prompts.
- Skipping access rules. The 'just for our team' app is public to anyone with the link.
- No way to edit a record. You can create things but you can't fix typos without an engineer.
07
What AI forgot to ask you
- Who's allowed to see this? Specifically by email or role.
- What happens when someone submits the wrong thing? Edit, delete, or escalate?
- Where does the notification go? A person, a channel, an inbox?
- What does success look like for the first user — and how will you know they used it?
08
Before real users see it
- I can sign in. I can sign out. The wrong email cannot.
- I can create, read, update, delete the main thing.
- If the form fails, I see a clear message — not a stack trace.
- Someone on my team has used it without me sitting next to them.
09
Questions to sit with
- 1.Is this small enough to ship this week?
- 2.If I had to hand this to a teammate tomorrow, could they keep it running?
- 3.What's the cheapest version that proves the idea — and what am I tempted to add that I shouldn't?
Ready to app it?
Take this path into your tool of choice — and when you finish (or get stuck), share what you learned so the next builder doesn't reinvent it.
