Litiqo
Home/Services/Custom Software & Systems
Service 02 of 08

When nothing off the shelf fits how you work

Some businesses have a process that no product was written for. Rather than bending the business to the software, we build the software around the business.

Custom Software & Systems in practice
What is included

The work, spelled out

Scope is agreed in writing before anything starts. Nothing on this page is an upsell waiting at the end of the project.

01

Internal portals

Staff, vendor, partner and customer portals with the roles, approvals and visibility each side is supposed to have.

02

Workflow systems

Multi-stage processes with rules, approvals, escalations and an audit trail, replacing the spreadsheet and the email chain.

03

Admin panels

Control surfaces for operations teams, built for speed of use rather than screenshots in a pitch deck.

04

Document flows

Generation, approval, versioning, signature routing and archiving, with the record attached to the thing it belongs to.

05

Dashboards

Role-based reporting that answers the questions leadership actually asks, from the live data rather than a monthly export.

06

Integrations

Connections to accounting, payment, logistics, messaging and government systems where the interfaces exist.

How it runs

Six stages, in this order

Discovery

We sit with the people who do the work and map the process as it is, including the parts that are officially not supposed to happen.

Specification

A written specification with screens, rules, roles and edge cases. You approve this before a line of code is written, and it is what we are held to.

Architecture

Data model, integrations, access control and hosting decided up front, so the system can grow without being rewritten.

Build in stages

Working software delivered in reviewable stages. You use each stage, and feedback lands while it is still cheap to act on.

Testing and migration

Test with your data, not sample data. Migration is rehearsed, reviewed and only then run for real.

Rollout and handover

Training per role, documentation, a support window, and an honest conversation about what comes next.

What you get

Handed over at the end

Every engagement ends with you holding the work, the access and the documentation. Nothing stays locked to us.

  • Written specification you approve before build
  • Staged releases you can use and review
  • Role-based access designed with you
  • Migration of existing data where it exists
  • Training per role and written documentation
  • Source code and infrastructure access handed over
Questions

Before you ask us

Against the approved specification, with the scope written down. Changes after that are quoted separately rather than absorbed silently and reappearing as a delay.

You do, on completion. We hand over the source and the infrastructure access, and we say so in the contract rather than leaving it vague.

Custom systems are built to be changed. That is the point of having one. Later changes are quoted like any other work, against a system we already know.

Sometimes. We review what exists and tell you honestly whether it is worth extending or whether a rebuild costs less over two years than the maintenance would.

Usually the first reviewable stage lands within weeks of the specification being approved. You should be using part of it long before the whole thing is finished.

Start here

Tell us what you are trying to fix

Not the feature list. The problem. We will tell you what it takes, what it costs, and whether one of our seven platforms already does it.