Apps

Internal tools without code: what to build first

The short answer

Build first the tool that replaces a daily routine several people share, where a miss costs money. Keep version one to one list, two or three views and one automatic step, with a named owner.

4 min read

Which tool should you build first?

Where does work get missed most?
App

A customer requests desk

It replaces a shared inbox and a "who's got this?" chat. The step that earns it: each new email sorted by kind and priority.

Read: How to build a customer requests desk from your inbox

App

An invoice tracker

It replaces a sheet of coloured cells. The step that earns it: a reminder drafted when an invoice goes late.

Read: How to build an invoice tracker

App

A lead list

It replaces leads buried in email threads and notes. The step that earns it: new enquiries added from email each morning.

Read: How to build a simple CRM without code

What kind of request?
App

An approvals list

It replaces requests by message and a reply "ok". The approver gets one list; the asker gets a status.

App

An onboarding checklist

It replaces a document copied for each new client or hire. Tasks are created and assigned on day one.

Not sure? Score your candidates

List every spreadsheet, shared inbox or "send me a message when" routine your team runs. Score each 1 to 3 on four questions and build the highest total first.

QuestionScores 1Scores 3
How often is it touched?MonthlySeveral times a day
How many people touch it?Just youThe whole team
What does a miss cost?An annoyanceMoney or a customer
How messy is it now?A tidy sheetFive tabs and "ask Sam"

How to build your first internal tool without code

  1. Step 1: Define the record before the screens

    What is one item (a request, an invoice, a lead) and which fields does it need?

    Watch out. Screens built before the fields are settled get rebuilt every time a field changes.

  2. Step 2: Pick two or three views

    The view you work from daily, a board by status, and everything. Not ten.

  3. Step 3: Add one automatic step

    The one that removes the most typing or the most forgetting. Add a second only after a week of use.

    Do this step in 50agents

    Keep track of customer requests and draft the replies

    Build it

    Captain builds the list, views and numbers, plus up to three AI agents or browser agents. Each change is a version you can undo, and any list exports as CSV. See the ready-made version.

  4. Step 4: Set access properly

    A shared link is not access control. Add people by account and decide who can edit before you invite anyone.

  5. Step 5: Name an owner

    One person who fixes it when it breaks and decides what changes. Tools without an owner rot by month three.

  6. Step 6: Retire the old way

    Archive the sheet or the label the day the tool goes live. Two systems for one job means the new one loses.

What can go wrong

  • Version one does everything

    Ten views and five automations, and nobody uses it. Ship one list, two views and one automatic step.

  • Everyone sees everything

    Salaries or customer details are open to the whole team. Set roles before you invite.

  • The automatic step runs unchecked

    An AI agent sorts or drafts wrongly for weeks before anyone looks. Read its work daily for the first week, then weekly.

Questions people ask

What internal tools should a small team build first?

The one replacing a daily, shared routine where a miss costs money: usually a requests desk, an invoice tracker or a lead list.

No-code or low-code for internal tools?

No-code when the tool is lists, views and simple automatic steps. Low-code when you need custom logic or many integrations a developer will maintain.

How do I stop an internal tool from becoming a mess?

One owner, a short list of fields, and a rule that every new view or step replaces something rather than adds to it.

Who should own an internal tool?

One named person who fixes it when it breaks and decides what changes. Tools without an owner rot within a few months.

When do we retire the old spreadsheet?

The day the tool goes live. Archive the sheet or the label, because two systems for one job means the new one loses.

How many views does version one need?

Two or three: the list you work from daily, a board by status, and everything. Not ten.

Read next

Or let Captain build it

One sentence to Captain. Free to start.

Build it with Captain
Internal tools without code: what to build firstBuild it