Skip to main content
Web // Custom software

Retire the spreadsheet that runs your company.

Every business has one: a shared spreadsheet with macros, color codes, and a single person who understands it. We turn it into a proper application with permissions, history, and an API.

anvexisstack.com/web/custom-software
Replaces
Spreadsheets · email chains
Adds
Permissions · audit · API
Integrates
ERP · CRM · identity

Same workflow, real database, proper permissions, no more 'who overwrote row 400?'

Good candidates for custom tools

Approval workflows

Requests, multi-step approvals, and notifications with a full history.

Operational dashboards

Live numbers from several systems in one place.

System glue

Small services that move data between tools reliably.

Partner portals

Secure access for customers, suppliers, or agents.

If a spreadsheet has a 'DO NOT TOUCH' tab, it's already software. It just doesn't have tests.
Anvexis Stack field observation

Why custom software, and when not

Off-the-shelf tools cover most needs, and we recommend them whenever they fit. But every business has a few processes that make it different: a quoting method, a scheduling rule, an approval chain. When those are forced into generic tools, they end up in spreadsheets, email threads, and workarounds that only one person understands.

Custom software makes sense for exactly those processes. A focused internal tool can replace a fragile spreadsheet, connect systems that don't talk to each other, or give a team one screen instead of five.

We keep custom builds small, well-tested, and connected to the systems you already have, so they remain an asset rather than a maintenance burden.

Build or buy?

SituationUsually
Standard process (payroll, email, accounting)Buy
Standard process with small tweaksBuy and configure, or extend
Process that differentiates your businessBuild
Glue between existing systemsBuild a focused integration
Spreadsheet that has become criticalBuild a proper tool

What we typically build

Internal tools

Quoting, scheduling, approvals, and operations dashboards built around your process.

Integrations

Connectors between your ERP, CRM, e-commerce, and partner systems.

Customer and partner portals

Self-service access to orders, documents, and status.

Reporting tools

Dashboards and exports that pull from several systems at once.

How a custom build runs

  1. Step 01

    Discovery

    Week 1–2

    Watch the current process, collect examples, and agree the scope.

  2. Step 02

    Prototype

    Week 2–3

    A clickable prototype to confirm screens and flow before code.

  3. Step 03

    Build

    Week 3+

    Two-week iterations with a demo at the end of each.

  4. Step 04

    Launch

    Final week

    Data migration, training, and a supported go-live.

  5. Step 05

    Support

    Ongoing

    Fixes and improvements under a maintenance plan.

Scope at a glance

Included

  • Discovery, prototype, and build
  • Integrations with existing systems
  • Testing, deployment, and training

Not included

  • Replacing systems that work well
  • Open-ended feature lists without priorities

Common pitfalls we help you avoid

The first pitfall is rebuilding something that already exists. We check available tools and your ERP's capabilities before writing any code.

The second is building without the people who do the work. Users join demos every iteration, so the tool fits their real process rather than an assumption.

The third is software with no owner. Every tool needs someone responsible for priorities and a plan for maintenance after launch.

What we measure

MeasureWhy it matters
Time per taskBefore and after the tool
Error rateMistakes the tool prevents
AdoptionShare of the team using it daily
Support requestsSigns of confusion or missing features

Who does what

We handle

  • Design, development, and testing
  • Hosting and deployment
  • Documentation and training

Your team handles

  • A product owner for priorities
  • Users for feedback in demos
  • Decisions on process changes

A worked example

Picture an engineering firm that prices projects in a spreadsheet with dozens of tabs. A custom quoting tool captures the same logic, pulls rates from the ERP, keeps every version of a quote, and generates the client PDF.

Estimators work faster, the formulas are tested, and a quote can be traced back to the inputs that produced it.

What success looks like

Success is a tool your team prefers to the spreadsheet it replaced, with fewer errors and a clear owner for its future.

Typical technology choices

LayerCommon choiceWhy
InterfaceReact and Next.jsFast, accessible, widely understood
ServicesPython or Node.jsMature libraries, easy to hire for
DatabasePostgreSQLReliable, flexible, and free
HostingYour cloud or oursMatched to your policies and budget
IntegrationREST APIs and webhooksWorks with Odoo and most SaaS tools

Myths we hear

Myth: Custom software is always expensive.

Reality: A focused tool that replaces a fragile process often pays back quickly. The expense comes from unclear scope, which discovery prevents.

Myth: Once built, it's finished.

Reality: Software needs updates for security, dependencies, and changing processes. A modest maintenance plan keeps it healthy.

Myth: Low-code tools make developers unnecessary.

Reality: Low-code is great for simple apps. Complex logic, integrations, and scale still benefit from conventional code.

Before you start

  • The process written down, even roughly
  • Example inputs and outputs, such as spreadsheets or forms
  • The systems it must connect to
  • Who will own the tool after launch

Questions to ask any provider

  • Who owns the code and the hosting accounts?
  • How will the tool be maintained after launch?
  • How are changes requested and prioritized?
  • What happens if the original developers leave?

Keeping it maintainable

Every tool we build lives in version control, ships through an automated pipeline, and comes with tests on its critical paths and a short guide for whoever maintains it next. Dependencies are kept current, so the tool doesn't quietly become a security risk.

Quality standards we build against

Internal tools are often built quickly and then maintained for years. We follow the practical test pyramid described by Ham Vocke: lots of small, fast unit tests, a moderate number of coarser tests, and very few end-to-end testsSource [1]. It keeps changes cheap long after launch.

Accessibility matters for internal tools too, because your colleagues use them every day. We build to WCAG 2.2, the W3C Recommendation published in December 2024, built on the four principles of perceivable, operable, understandable, and robustSource [2].

Frequently asked questions

Should this be in our ERP instead?
Sometimes yes. We check whether an ERP module fits before proposing a separate app.
Can it use our company login?
Yes, via single sign-on with your identity provider.
How do you migrate the spreadsheet data?
We map, clean, and import it, then run both in parallel briefly.
What does maintenance look like?
Dependency updates, security patches, and small changes, through a support plan or your team.
Can it grow later?
Yes. Clean architecture and an API make extensions straightforward.
Who owns the code?
You do. The code lives in your repository, and you can maintain it with any team.
Can custom tools connect to Odoo?
Yes, through Odoo's API, so data stays consistent between the tool and the ERP.
What technology do you use?
Usually TypeScript with Next.js or React for interfaces, and Python or Node for services, chosen to suit your team.
How do you estimate cost?
After discovery, with a fixed price for a defined scope or a team-based budget for evolving work.
What if requirements change mid-build?
Two-week iterations make change normal: priorities are reviewed at every demo.
Can you build on top of our existing database?
Yes, with care. We review the schema and add an API layer so the new tool doesn't depend on fragile direct access.
Do you provide hosting?
We can host and maintain the tool, or deploy it to your infrastructure and hand it over.
Can we start small?
Yes. A first release covering one workflow often delivers most of the value and informs the next steps.
Do you sign NDAs?
Yes. We're happy to sign a mutual NDA before discovery begins.
Can you integrate with legacy systems without APIs?
Often, through database access, file exchanges, or a small adapter service, assessed during discovery.
Can our IT team host it?
Yes. We provide deployment instructions or containers, and can support your team through the first releases.
What about user access and roles?
Tools include login, roles, and permissions from the start, often connected to your existing single sign-on.
How do you keep custom software maintainable?
Typed code, a balanced test suite, documentation, and simple architecture that another team can pick upSource [1].
Do internal tools need to be accessible?
Yes. Employees use them daily, and building to WCAG 2.2 makes them usable for everyoneSource [2].

Sources

  1. [1]The Practical Test Pyramid (opens in a new tab)Ham Vocke, martinfowler.com, 26 February 2018
  2. [2]Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)W3C, 12 December 2024