FAQ
The questions we get asked before a first call
If yours is not here, ask it directly — we would rather answer it than have you guess.
Working together
- It means we design the checks and balances at the same time as the workflow, not after it. Approval limits, separation of duties, and audit trails are built into the system itself, so control does not depend on someone remembering to do the right thing.
- No. Plenty of engagements are process work alone — mapping how you operate, fixing the sequence, and tightening controls on the systems you already have. We recommend an ERP only when the problem is genuinely one of disconnected systems rather than of process design.
- The diagnostic phase is light: interviews and observation, mostly around your team’s existing schedule. Implementation is staged so you are never running two systems in full at once. We agree the cutover window with you and are present through go-live.
- Complexity matters more than headcount. A five-person importer running inventory across two locations, buying in USD and selling in TTD, needs more system than a thirty-person service business with one revenue stream. What we look for is inventory, imports, multi-currency, VAT obligations, or more than one revenue stream. Any two of those and there is usually a case worth examining. If your operation is genuinely simple, we will tell you that a smaller fix beats an ERP.
- No, and deciding who does is part of the design work. Some roles need to create and approve records. Others only need to be visible in them — a driver on a delivery, a picker on a stock move. We scope access by role, which keeps the system simpler to run, the training shorter, and the rollout smaller than most owners expect.
Scope and timing
- A focused single-department implementation typically runs eight to twelve weeks from diagnosis to go-live. A multi-entity or multi-warehouse rollout runs longer. We give you a staged timeline at the end of the design phase, before you commit to the build.
- The diagnostic is a fixed fee, so you know the cost before you start. Implementation is quoted per stage against the agreed design, which means no open-ended hourly billing and no surprises halfway through. You approve each stage before it begins.
- That is the expected outcome, and we configure with it in mind. Odoo scales by adding modules rather than replacing the core, so adding manufacturing or a second location later is an extension, not a rebuild.
The region
- Yes. VAT treatment, filing periods, and the supporting documentation are configured as part of the build rather than handled outside the system in a spreadsheet. The audit trail behind each return stays intact.
- Standard. Purchasing in USD while selling in TTD, landed cost across duty and freight, and long supplier lead times are configured from the start.
- Yes, across the wider Caribbean. Discovery is most effective on site, so regional engagements usually pair an on-site diagnostic visit with remote delivery for the build and training phases.
Still deciding whether to call?
A first conversation costs nothing and commits you to nothing. Worst case, you get an outside opinion on where your process is leaking time.
Or call 323-AURA · 868-323-2872