Services / Internal tools

Internal tools and dashboards.

We build software for the tasks your team does every day: tracking jobs, managing customer records, approving work and reporting on progress. Each tool uses the information and permissions needed for that job.
Start a conversationExplore the scope

When a spreadsheet has become a shared application.

An internal tool is useful when several people need to update the same records, follow a process or work with information from different systems. We review whether your existing software can do the job before proposing a custom application.

Problems this work can address

  • A shared spreadsheet holds job status, approvals and customer details.
  • People need to check several systems to answer a simple question.
  • Important changes are buried in emails and chat messages.
  • Managers spend time combining data before they can review progress.

Scope

What we can build with you.

We establish which parts are useful for your business and what your existing tools can already do before agreeing the build.

  • Job and pipeline tracking

    Searchable records showing status, ownership, next steps and relevant documents. Teams can update work without maintaining separate spreadsheets.

  • Dashboards and reports

    Views for sales, delivery or management, using agreed definitions for each measure. We show when data was last updated so reports can be interpreted properly.

  • Approval processes

    Requests, review steps and decisions in one place. Permissions and a history of changes make it clear who can approve work and what happened.

  • Data entry and administration tools

    Forms with required fields, checks and bulk actions for recurring tasks. The interface connects to the existing CRM or database where appropriate.

  • Access for different roles

    Agree what each role can view, edit and export, then implement and test those permissions with representative users.

  • Hosting, training and handover

    Set up the agreed hosting, document deployment and maintenance, and train the team on daily tasks. Access and support responsibilities are recorded.
Two people working at a desk behind reeded glass in warm evening light

In practice · Recruitment agency

Internal applications and sales dashboards.

The recruitment project included custom applications and dashboards for pipeline visibility, team tracking and rewards, alongside the agency’s website, CRM and automation.

Read the case study

Start with the daily task. Test the tool with its users.

The people using the application help define the screens and try them during development. We agree the first release around a manageable set of tasks.

  1. Scope

    Map tasks, data sources, roles and required screens.

    Your involvement: Show the current tools and a typical working day.

    Screen plan, priorities and quote

  2. Build

    Build the application and connect the agreed data sources.

    Your involvement: Review working screens with the team.

    Application available for review

  3. Test

    Check permissions, data changes and reporting accuracy.

    Your involvement: Try normal tasks and unusual cases.

    Tested release and user instructions

  4. Launch

    Release the application and provide training and access.

    Your involvement: Nominate administrators and introduce the tool.

    Live tool and maintenance plan

After launch

We agree launch aftercare, handover and any ongoing maintenance or development with you. Your organisation retains access to its code, accounts and documentation.

Support and ongoing development

Planning the work.

Bring the spreadsheet or the process it supports.

We can work through who uses it, what they change and where the information comes from. That gives us a basis for recommending an existing tool, a small application or a phased replacement.
Can an internal tool use our existing database or CRM?

Yes, where the system provides suitable access. We check its API, permissions and update rules during discovery. A separate database is introduced only when the application needs one.

How is this different from a larger custom software project?

An internal tool usually focuses on a defined set of staff tasks. A wider custom software project may replace a core system, serve customers as well as staff and require migration across several departments.

How long does an internal tool take to build?

The number of screens, data connections, permission rules and migration work determine the schedule. We agree milestones after reviewing the process and can phase the work so the first release covers the most useful tasks.

Can our team change the tool later?

We agree which settings, reports and records administrators can change themselves. Changes to application behaviour may still need development work. You receive the code and documentation, and can use your own developers or ask us to continue.

How can we help you work better?

You don’t need a brief or a solution in mind. Tell us what’s proving difficult or what you’d like to improve. We’ll explore the options together and agree where to start.

Start a conversationHow we work