Intactic

Capability

One record, reconciled.

Finance, inventory, purchasing and people held in one system that agrees with itself. Reporting becomes a query rather than a project.

Typical engagementAssessment, then build
Team3–5 people
First phaseAudit, 2 weeks

The problem

Operations fail by drift, not by crash.

A stock figure that is two days behind. A purchase order approved in an email thread. A month-end close that takes nine days because three teams keep their own version of the truth.

Buying an ERP solves the shape of the problem and creates a new one: configuration, consultants, and a system nobody in the business can change without a change request. We take a narrower route, starting with the numbers that hurt.

System map
Inventory
Purchasing
Payroll
Approvals
CoreLedger
Banks
Tax
Reports
Audit
Ledger at the centreerp

Deliverables

What we build.

Six pieces of work, scoped in discovery and delivered in two-week increments.

Chart of accounts

Structures that match how the business is managed, not only how it is audited.

Inventory and purchasing

Locations, movements, reorder rules and approval limits that reflect real authority.

Payroll and HR interfaces

Clean boundaries with the systems that already own employee data.

Approvals and permissions

Role-based access, delegations, and a record of who approved what, and when.

Integrations

Banks, logistics, tax portals, and the spreadsheet that will not die.

Operational reporting

A small set of reports people open every morning, and no more than that.

Approach

How we work on it.

Three working rules that shape the build, and the stack we usually reach for.

One owner per number

Every figure has a single system of record. Where two systems disagree, the reconciliation is part of the build, not an afterthought.

Start with the close

We work backwards from month-end. If the close is clean, the rest of the reporting can be trusted.

Changeable by the business

Approval chains and report definitions live in configuration, not in code that requires us to change it.

Typical stack

PythonDjangoPostgresCeleryMetabaseOdoo

Odoo or an existing ERP stays where it earns its keep. We build the parts that are specific to you and connect the rest.

How it starts

A two-week audit of the current close: where the numbers come from, where they disagree, and what it costs to fix each one.

Scope this work

Related

Usually built alongside.

Most engagements combine two or three capabilities; these are the pairs we see most.

Next step

Tell us what you’re building.

Send a short brief. You get the questions that matter, a rough shape of the work and a straight answer on fit.