Purchasing & suppliers
Supplier records, purchase approvals and expected receipts linked to the goods the business needs.
Services / Custom ERP development
Custom ERP software for connected business operations.
Connect purchasing, stock reservations, fulfilment and financial handoffs. We build the ERP workflows your business needs and integrate the systems you retain.
Scope & fit
Choose the first cross-team operation to connect.
A custom ERP is worth considering when important workflows span departments, locations, or business units and cannot be supported by configuring existing software. We examine what to retain, integrate, and build before defining a replacement.
Inventory & orders
Available stock, reservations, fulfilment and returns connected to the same order, with shortages assigned for resolution.
Logistics & finance
Delivery records linked to orders and exchanged with accounting under agreed document, currency and reconciliation rules.
Operational controls
Roles, approval limits and action history that show who may change a record and who resolves an exception.
Is this service right for you?
- Best fit:
- Operations teams reconciling orders, stock and approvals across disconnected tools.
- First useful result:
- One order-to-reservation workflow with customer status and an exception report.
- What can stay:
- Keep accounting; agree which system owns each record and update.
- Scope to agree:
- Rollout across multiple sites, forecasting and accounting replacement are scoped separately.
- To get started:
- Bring order examples, stock rules, source IDs and the person who approves exceptions.
Migrate orders, stock and balances with reconciliation.
We map products, suppliers, stock, orders, balances and the history to retain. Trial transfers check records, relationships and totals before we agree the cutover, parallel operation and recovery steps.
See delayed orders, available stock and blocked approvals.
We build reports on late orders, stock available after reservations and approvals awaiting action. Reports can run in the ERP or your BI environment; calculation rules and selected totals are checked against source records.
Example first release / Orders and stock
One order connects sales, stock and delivery.
A distributor keeps customers in a CRM, orders in spreadsheets and stock in a warehouse tool. We start with one complete order workflow, connecting the systems the team keeps.
- 01
Capture the order
Customer, items and agreed terms in one record.
- 02
Reserve available stock
Allocate available quantities and assign any shortage for review.
- 03
Record the dispatch
Link shipped quantities and documents to the order.
- 04
Show the next action
Make open quantities, delays and responsible people visible.
Reliable records at every handoff
We agree identifiers, record ownership and update frequency. Trial imports check totals, failed exchanges, restricted access and overdue-order reports before the pilot enters daily use.
A pilot the team can accept
The pilot starts with one team. Our delivery lead prepares checks and recovery steps; your operations owner accepts the scenarios and approves launch. Together we assign first-week support and decide when to retire the old workflow.
Connected systems. Clear ownership.
- Operational ERP
- Accepted orders, progress and exceptions. Stock ownership changes only after the pilot reconciliation passes.
- Existing accounting
- Posted financial entries and payments stay in accounting. We define the exchange and checks; an ERP finance screen does not replace the ledger or tax reporting.
Before daily use, agree warranty fixes, paid support, hosting, access and documentation. Extra warehouse workflows and forecasting can follow in later releases.
Before you decide
Configure, connect or build?
A custom ERP is worth considering when a standard product cannot support your operations. We help you compare the options.
Selected work
Software built around real business operations.
Explore purchasing, stock and financial workflows in GBA, and structured engineering records and reporting in LENS Data Explorer.
Retail & cross-border operations
Global Business Assistant
ERP and CRM for trading businesses, bringing purchasing, sales, warehouse operations, delivery and settlements into one system. Shared order, stock and payment records help teams coordinate their work, cross-border operations and multi-currency accounting.
ExploreEngineering & infrastructure
LENS Data Explorer
An engineering data platform for WestConnex New M4 Tunnels in Sydney. Asset hierarchies, equipment, cable networks, drawings and revision history share one working environment. Engineers locate components, inspect their connections and prepare reports from a common infrastructure model.
ExplorePlanning guides
Plan scope, integrations and launch.
Connect CRM and ERP with clear ownership
Follow one order through retries, late updates and conflicting data before defining your own exchange.
Budget the first operational ERP release
Compare order and stock modules, define the accounting boundary and include the work needed for rollout.
Choose the right ERP approach
Compare configuring an existing product, connecting your systems, and building around distinctive operations.
Make reports agree across systems
Define sources, formulas, update times, and reconciliation for connected operational reporting.
Reporting definition templatePrepare for a phased transition
Define one operational loop, assign ownership and use evidence to decide when to launch or expand.
ERP pilot acceptance sheetBudgetStarting budget Payment model After launch
Price one connected operation before expanding the ERP.
Reservations, partial deliveries, returns and financial handoffs change an ERP estimate even when the screen list stays the same. Scope the first order flow, the locations using it and the systems that remain. Include reconciliation and report acceptance alongside development.
From USD 50,000
For a full custom software project. We estimate your agreed scope before work begins.
Hourly or fixed price
An hourly team for evolving work, or a fixed price for a clearly defined module.
Plan operating costs
Paid support, hosting and third-party services are scoped separately from development.
Start with the context you already have.
Bring a normal order, one exception, stock rules and the accounting interfaces available. An operations or finance owner can help decide which results must agree before the new workflow enters daily use.
Questions
Questions about this service
Do we have to replace every existing tool?
No. We assess which tools to retain, connect or replace around one complete operational process. The first release includes its required integrations and data checks. Other departments or locations can follow after the team has tested and accepted that workflow.
Can you migrate historical records?
Yes, subject to source access and data quality. We agree the history to retain, run trial imports and reconcile records, relationships and balances with your data owners. Unresolved exceptions, cutover checks and recovery steps are recorded before the transfer enters daily use.
Can we keep our current reports?
Often, yes. We inspect the report definitions and data connections, then decide whether to retain the tool, reconnect it or rebuild selected reports. Historical periods and control totals are compared before switching; any accepted changes to calculations or presentation are documented.
How do you check that report totals are correct?
We agree each measure’s formula, dates and included records, then compare test results with underlying orders, stock movements or payments. Differences are investigated with finance or operations. Accepted examples become checks for later releases.
Can we launch one ERP workflow before the whole system?
Yes, if it can operate with retained systems. We scope a complete process with its data, integrations, permissions and reports, pilot it with the affected team and resolve issues before rollout. Results from that release guide expansion to further departments or sites.
How do you protect approvals and financial information?
Operations and finance define who may change stock, approve exceptions and access financial records. We implement those permissions and action history, then test both allowed and blocked actions. Launch checks also cover infrastructure access, backups and monitoring.
Will you help our team learn the new system?
Yes. We plan onboarding around the work each role needs to do, then prepare the agreed walkthroughs, instructions and administrator guidance. We help staff practise representative tasks before rollout and use their feedback to address confusing steps. Training and launch assistance are included explicitly in the delivery plan, so your team knows what help to expect.
Will you stay involved after launch?
Yes. We help arrange a support plan before release, with agreed coverage, a way to report issues and clear operating responsibilities. We can handle the agreed maintenance and help investigate problems, while reviewing user feedback with you for future improvements. Ongoing support and new features are priced separately, with the terms explained before the system enters daily use.
Your next system starts with a conversation
Tell us what needs to work better.
Share your processes, the systems you use today, and what you want to improve first. Our CEO normally leads the first discussion of possible approaches and what needs investigation before an estimate.
Europe, USA, Canada & Australia