ERP & Internal Tools Design Services

Design the screens your staff use all day — pricing a job, sending a crew, checking a site, tracking equipment, signing off spend — so each job takes fewer clicks, fewer spreadsheets and fewer calls to the office.

A steel robotic arm on a post pulls out the one orange drawer of a tall white ceramic filing cabinet.
Custom scope
Set in the service’s proposal
Designed with your staff
Office, site and floor
Your ERP stays
New screens on existing systems
Build-ready handoff
Task flows, states and prototype

In short

Operational tools that make the daily job faster, in the office, on site and on the floor.

What's included

  • Estimates and quotes
  • Work orders and tasks
  • Inspections and checklists
  • Asset records
  • Approvals
  • Tables and bulk actions

Answers you'll have before development

  • Which task costs your staff the most time?
  • What has to work on a tablet, on site?
  • Which spreadsheet can finally go?

Where it stops

Enterprise UX Design

The structure that holds many modules and departments together.

ERP & Internal Tools Design

The screens where staff do one operational job, fast.

Not included

  • A complete ERP or accounting engine
  • ERP integration or data migration

The job first, then the screen that does it

Internal tools go wrong when screens follow the database instead of the work. The design starts from what staff actually do, step by step, and where they do it.

Discuss your product
  • A white ceramic clipboard carved with a checklist, held by a steel clip, one tick in graphite.

    Task and workflow maps

    Each operational job step by step: who does it, where, and with what.

  • A stack of ceramic form cards carved with line items, held by a steel clip, a small graphite stamp on top.

    Estimates and work orders

    Forms that follow the work, with defaults, line items and saved drafts.

  • A white ceramic file cabinet, its drawer open on steel runners and full of record cards, one raised card in graphite.

    Records and dense tables

    Asset and job lists with filters, bulk actions and saved views.

  • A white ceramic tablet with a carved checklist and large buttons, held on a steel stand, a graphite stylus beside it.

    Field and tablet views

    The same job on a tablet, one-handed, with a patchy signal.

You receive

  • Task flows for every role
  • A state and permission matrix
  • UI and a clickable prototype
  • Walkthroughs with your engineers

Designed for the hundredth time that day, not the first.

Internal tools design is measured in the work people repeat: the same estimate, inspection or approval, many times a shift. Every screen is built for speed on a good day and clarity on a bad one.

Every screen is designed for

  • Draft saved, not submitted
  • Waiting for approval
  • Rejected, with a reason
  • Required field missing
  • No signal on site
  • Record changed by someone else
  • Task overdue
  • Bulk update on many records
  • Totals that do not reconcile

When ERP and internal tools design is the right frame

It fits when your own staff run the business through the software, and every wasted click repeats all day.

  • Staff repeat the same jobs

    Estimates, work orders, inspections or approvals, many times a day.

  • Spreadsheets fill the gaps

    People copy data between the system, sheets and chat to finish the job.

  • Work happens off the desk

    On site, on the floor or on a tablet, not only in the office.

  • The back end stays

    Your ERP or database remains; the screens on top of it change.

Let's give your staff back the hours the tool takes

Tell us which job your team repeats most and where it slows them down. We will come back with the service that fits and a realistic next step.

Scope, access and who does what

Internal tool work usually goes module by module, through one of our services, starting where staff lose the most time. Its proposal sets the terms.

Scope
Per service fixed or phased, set in the proposal
Timeline
Agreed after scope, access and dependencies
  1. You provide

    The tool
    Access to the current system, or screenshots and exports, with a test account per role.
    The work
    Time with the staff who do the job, and sample estimates, orders and inspection forms.
    Decisions
    An operations lead who knows the jobs, and a product owner who can sign off changes.
    Engineering
    The ERP or database behind the tool, its integrations, and what can change.
  2. Who does what

    ANODA
    Maps each job with the people who do it, designs the task flows, states and screens, and documents what engineering needs.
    Your team
    Opens the door to staff and data, reviews each step, builds and integrates the tool, and trains the people who use it.
  3. Boundaries

    Outside internal tools design
    Development, ERP configuration, integrations and data migration, accounting logic, and staff training.
    After the design
    Your team or partner builds and integrates the tool. Implementation reviews are scoped separately when needed.

In the client's words

ANODA organised a complicated installation workflow into screens we could review role by role. Estimates, project progress and punch lists were considered together, which gave us a concrete way to discuss how the proposed product should support work on site.

Yidi Srulowitz cabinit LLC Read the Cabinit case

Which job takes your staff too long?

Tell us what the tool is for, who uses it and where, and which spreadsheets it has not replaced.

What do you need? *
Project budget (USD) *

What is your product, who uses it, and what would you like us to do?

    Within 15 minutes, we’ll reply with initial feedback and follow-up questions.

    Read more about operational software

    All articles

    ERP & Internal Tools Design: common questions

    Before hiring for ERP design services, what work should we ask a team to walk us through?

    Ask to see an operational job designed end to end — an estimate, an inspection, a work order — with the states around it: a draft, a rejection, a missing field, no signal on site. Ask whether the team spoke to the staff who do the work, how it handled dense tables, and what it did on a tablet. Ask which tools were live, and what was redesigned rather than started fresh. Our Cabinit, Qarma and Vecna cases show that range.

    What would ERP design cover for our jobs and roles, and what sets the size of the work?

    Task and workflow maps with the people who do the work, the roles and permissions, the forms for estimates and work orders, inspection and checklist flows, records and tables with filters and bulk actions, the field or tablet views, and the UI with a clickable prototype. Cost and timeline depend on the number of jobs and roles, how dense the data is, the platforms, and how much of the current tool stays. Work is often phased by module and set in the proposal for the service you start with.

    Which roles and workflows does internal tools design cover?

    Office staff who estimate, plan and schedule; site managers and field teams who inspect, report and close tasks; warehouse and operations leads who watch the work live; approvers and finance who sign off; administrators who manage records, assets and access. The workflows are the ones that run the business: quoting, raising and assigning work orders, inspecting against a checklist, logging defects, keeping asset records current, approving and closing work.

    Which ANODA services fit an internal tool, and where do we start?

    It depends on what you know. A UX Audit shows where the current tool slows people down; Usability Testing lets you watch staff use it. Web App Design and Mobile App Design cover the office and the field, Dashboard Design the managers' view, and Product Redesign replaces a tool while staff keep working. When several modules and departments need one structure first, Enterprise UX Design comes before any single job. Web App Development builds the result.

    How does operations software UX handle complex states, permissions and data?

    With the task, not after it. Every screen is drawn for a saved draft, a request waiting for approval, a rejection with its reason, a missing required field, no signal on site, a record someone else changed, an overdue task, a bulk update and totals that do not reconcile. Permissions follow who approves what and up to which amount. Tables are designed for real volume — hundreds of rows, long codes, empty fields — and forms keep the defaults and shortcuts power users rely on.

    What do you need from our team to start?

    Time with the people who do the work — in the office, on site, on the floor — and sample documents: estimates, work orders, inspection forms. Access to the current system, or screenshots and exports if that is easier. An operations lead and a product owner with the authority to decide, and the engineers who know the ERP or database behind the tool and what it lets us change.

    Which operational tools have you designed?

    Cabinit, a kitchen-installation platform — 250 unique screens and 5 roles in one system. Qarma, a quality and compliance product — a web platform and one inspector app, designed across releases in 2021 and 2022. Vecna Robotics, a warehouse operations console — 192 unique screens. Each case study follows a working job — an estimate, an inspection, a robot setup — through the people and states around it.

    Can you redesign the tools our staff use without replacing the ERP underneath?

    Yes. We design the screens on top of the system you run, not a new engine: Qarma's design grew release by release through 2021 and 2022. Our designers work in your files, next to your engineers and the staff who use the tool each day, and hand over the task flows, the matrix and the components.