Systems of record
Odoo
One system of record, known properly, rather than three known partly.
What we implement
One system, every module
Odoo is modular by design, and that is the reason for choosing it: you start with what the business actually needs and add the rest when it asks, rather than buying a whole suite on day one.
One system of record, and we implement one. Depth in a single platform beats a menu of three known partly, and which ERP is not the interesting question anyway. The interesting ones are which modules, configured how, and what still has to reconcile at the end of the month.
Still running the business on spreadsheets and a dozen tools that do not talk to each other?
One system, instead of a dozen.
Sales. Accounting. Inventory. Manufacturing. Point of sale. The website. All of it in one place.
Sell a product on the website. The invoice is created. The stock moves. Nobody types it twice.
Start with one app. Add the next when the business asks for it, not before.
The repetitive parts get automated. The parts that need judgement still get yours.
And it costs a fraction of what the big suites charge, which is most of why we picked it.
In two minutes
Odoo, explained by Odoo
Their own introduction, which covers the ground faster than we can in writing. Two minutes.
What you can turn on
Forty-eight apps, one database
Odoo is a set of apps sharing a single database, which is why a sale made on the website reaches the ledger without anyone retyping it. Start with the two or three you need. The rest wait until the business asks for them.
Finance
- Accounting
- Invoicing
- Expenses
- Spreadsheet (BI)
- Documents
- Sign
Sales
- CRM
- Sales
- POS Shop
- POS Restaurant
- Subscriptions
- Rental
Websites
- Website Builder
- eCommerce
- Blog
- Forum
- Live Chat
- eLearning
Supply Chain
- Inventory
- Manufacturing
- PLM
- Purchase
- Maintenance
- Quality
Human Resources
- Employees
- Recruitment
- Time Off
- Appraisals
- Referrals
- Fleet
Marketing
- Social Marketing
- Email Marketing
- SMS Marketing
- Events
- Marketing Automation
- Surveys
Services
- Project
- Timesheets
- Field Service
- Helpdesk
- Planning
- Appointments
Productivity
- Discuss
- Artificial Intelligence
- IoT
- VoIP
- Knowledge
We do not switch all of it on. Most engagements run four to eight apps at go-live, and the ones nobody asked for stay off, because an unused app is still a thing you have to upgrade.
How we work
Discovery, design, build, run
-
Discovery
We look at what you actually have, and what has to still be true afterwards. There is no meter running on discussion time here. You get as many sessions as it takes to understand what is being built and why.
-
Design
Written down before anything is built. Scope, the shape of the solution, and the things we have agreed not to do.
-
Build
In the open, against real data, in increments you can look at. Nothing arrives as a surprise at the end.
-
Run
Live, then supported. Monitored, maintained, and extended as the business changes.
Engagement
How this gets bought
Four ways
Fixed price, time and materials, retainer, or managed service. There is no minimum engagement size, so a single integration is a real conversation and not a rounding error.
What you are paying for
Senior people on the actual work, not a pyramid with one architect and fifteen juniors. Large firms charge a premium that has more to do with their overhead than with the quality of the delivery. The same work can be done properly for less, and that is the reason this company exists.