Micro web tools for small businesses

Small tool, clear job

Turn one repeated task into a focused calculator, portal, form, or internal screen. Keep the rules visible and the useful decision with your team.

One focused job Clear human control First version in 7 days

The problem

Too much work in the browser

When a team repeats the same calculation, qualification, lookup, or request step, a generic spreadsheet or shared inbox can become the bottleneck.

A micro web tool gives that one task a clear input, visible rules, and a useful output without pretending to replace the systems your team already relies on.

A focused first build

Define it, make it useful

  1. 01
    Choose

    Pick one task with a clear user, inputs, and result.

  2. 02
    Build

    Create the smallest usable screen, form, calculator, or portal around that task.

  3. 03
    Hand over

    Test it with real examples and leave the rules, ownership, and updates clear.

Example tools

Three useful first versions

Calculator

Quote builder

A small tool turns a structured brief into a consistent quote draft using editable pricing rules. The owner reviews the total, wording, and exceptions before anything is sent.

Portal

Client handoff page

A focused client page collects the right files and answers, confirms the next step, and gives the team a usable brief instead of another unstructured email chain.

Internal screen

Quick review queue

A compact internal screen brings the next items, missing details, and review status into one view. A person keeps control of prioritisation and final decisions.

Good first targets

One useful screen

  • Qualifying a request before a call or a handoff.
  • Calculating a price, estimate, or next action from known rules.
  • Collecting the information a team needs before starting work.
  • Giving a client a simple status, upload, or request page.
  • Putting one repeated internal review into a clearer queue.

Scope honestly

Keep it small

A useful first tool has one clear user journey, a limited set of inputs, and a named owner for the rules. It should make a task simpler, not recreate a whole operating system.

Complex permissions, high-risk data, regulated decisions, and large integrations need separate scoping before work starts.

Start with one real task

Show us the manual screen

Tell us what people do now, what they need to decide, and what a useful result would look like.

We reply by email after a quick scope check. Use sanitized examples for sensitive work.