Build an internal tool for your team (without coding)

An internal tool is not a marketing site and not a client portal. It is a tool your team uses to work: track cases, approve requests, centralize information, avoid mistakes.

Often it replaces:

• an Excel file that became a monster
• a Slack channel where nobody finds anything
• three poorly connected tools
• “ask Marie, it’s in her head”

You can absolutely build it alone. It is not reserved for large teams. If your need looks more like a business tool for your activity (quotes, field jobs, scheduling), also see Build a small online tool for your business.

When an internal tool is worth it

Yes, if:

• the same process repeats every week
• information is scattered or fragile (spreadsheet, messages, “it’s in someone’s head”)
• mistakes cost time, money, or quality
• you want one place to track progress

If the process changes every week, or a simple board still works, wait a bit. Otherwise, you can start.

Start with a simple first version

Do not try to cover the whole company. First describe one problem, in concrete words.

Example:

Today, to track support requests, we waste time because everything lives in Slack. I want a tool where we create a request, handle it, and clearly see what is urgent.

If several people will use it, also say who does what (for example: the agent handles requests, the manager approves).

For this first version, stick to the basics: see the list of requests, open one, create a new one. Three or four statuses are enough (for example: to do, in progress, done). If you want to go deeper on this “intentionally limited first version” idea: What is an MVP?.

Accounts and access

As soon as there is team or client data:

• a salesperson does not necessarily see HR information
• an intern should not be able to edit everything
• an external client does not enter this tool (for them, build a separate client portal)

On Index10, enable Index10 Cloud, then test with a second account to check that each person only sees what they should.

Later, if you connect automatic emails (or another external service), you may be asked for a secret code. Never paste it in the chat: store it in Cloud, under Secrets. Details: Cloud · Security.

Getting people to use it

A nice tool is not enough. It has to be used for real.

If you are alone: test it on real cases for a week, then fix what wastes your time.

If other people will use it:

1. Pick 2 pilot users (not the whole company at once).
2. Have them use it on real cases for a week.
3. Fix what gets in their way.
4. Only then expand.
5. Name an owner (even 30 minutes a week).

Without someone who owns the tool, it often dies quietly.

How to do it on Index10 (with a team)

1. Explain the work with a concrete example (“when a request arrives…”).
2. Let it build a first version, then click through the preview.
3. Enable Cloud. Create one test account for each type of person (e.g. sales / manager).
4. Publish to get a link you can share with the team.
5. Share that link internally (often enough to start).
6. Improve what comes back every week; leave one-off requests aside.

You can start with a simple message, for example:

I want a tool to track my support team’s requests: create a request, see where it stands, and mark it when it’s done.

More on how to phrase requests: What is a prompt?.

Useful first versions

• Ops / field: job tracking + status
• Support: request queue + priority
• Light HR: new-hire onboarding tracker
• Sales: simple lead tracking (not a giant sales software)
• Nonprofit / club: member or volunteer tracking

Common traps (and why they hurt)

• Trying to do everything at once: too many screens, too many edge cases. The tool is never “ready,” nobody switches.
• Copying the spreadsheet as-is: you keep the same mess in a new interface. Simplify the process first.
• No way to get the data out: people stay on Excel because they fear losing history. Plan a simple export from day one.
• Mixing internal tool and public site: visitors and the team do not need the same things or the same permissions.

In short

An internal tool succeeds when it saves time on a real process, with clear permissions and real adoption. On Index10: one process, role tests, pilots, Cloud, publish, then expand.

The useful question: which spreadsheet or message thread does the team want to stop suffering through this month?