A real engineer replies
Tell us what's tangled. We'll help map the wires.
Share the problem, the systems involved, and what a better outcome looks like. A few useful details beat a 40-slide deck every time.
- Reply time, within business hours
- 12 hrs
- First call, no slide deck
- 30 min
- Fixed-price discovery sprint
- 2 wks
- Automated sales sequences
- 0
You write to us
A short note is plenty: the workflow, the systems, and what better looks like.
Start a conversation
Fields marked * are required. Everything else is optional.
Useful context to include
- The workflow or product you want to improve
- The systems and integrations involved
- What's slowing things down today
- Timing, budget, or technical constraints
Talking to a startup, not a sales team
Your message goes straight to the engineers who would do the work, not into a sales pipeline. We read every enquiry, reply personally, and if we're not the right fit, we'll say so and suggest where to look instead. There's no obligation and no automated follow-up sequence.
If you're not ready to talk yet, the labs and articles are a good way to frame the problem first. Come back whenever it's useful.
Good reasons to get in touch
| Situation | What we can help with |
|---|---|
| Starting with Odoo | Scoping, implementation, and a phased plan |
| Odoo that's slow or outdated | Performance tuning, upgrades, and cleanup |
| Too much manual work | Integrations, document AI, and automation |
| A product idea | SaaS, web, or mobile builds from discovery to launch |
| Fragile infrastructure | Backups, monitoring, CI/CD, and cloud setup |
What a first call covers
In thirty minutes we'll ask about the problem, the systems involved, who uses them, and what a good outcome looks like. You'll leave with our honest view of the options, whether or not we work together.
What happens after you write
No sales sequence, no pressure.
We read it
We read every message and reply within 12 business hours.
We reply personally
With questions, a suggested call time, or an honest pointer elsewhere.
A 30-minute call
We understand the problem and share our view of the options.
A short proposal
If it makes sense, a discovery sprint proposal with scope and price.
If you're comparing partners
Ask us anything you'd ask a larger firm: who would work on your project, how we handle scope changes, what happens after launch, and who owns the code. We're happy to answer in writing, and to talk to your technical team directly.
If you'd like to see how we think before a call, the case studies, articles, and tech radar show our approach in detail.
Helpful to have ready
- Which systems you use today, and which are staying
- Rough volumes: users, orders, documents, or locations
- Any deadline that matters, and why
- Who will make the final decision
What you can write to us about
Most messages are about a new project: an Odoo rollout or migration, an integration, an AI feature, a web or mobile product, or infrastructure work. We also welcome smaller questions: a second opinion on a proposal from another vendor, a review of an existing system, or advice on whether a project is worth doing at all.
If your request is outside what we do, we'll say so quickly and, where we can, point you to someone better suited.
Where to send what
| Topic | Best route |
|---|---|
| New project or estimate | The contact form on this page |
| Existing client support | Your support channel or shared tracker |
| Security report | The process described on the security page |
| Press or partnerships | The contact form, with a short note on the topic |
Not ready to talk yet?
That's fine. Our articles cover the most common decisions in detail, the labs let you sketch a business case or an architecture on your own, and the comparisons explain where Odoo fits and where it doesn't. Come back whenever a conversation would be useful.
Your details stay with us
We use what you send only to reply and, if we work together, to plan the project. No mailing lists unless you subscribe.
Frequently asked questions
How quickly will you reply?
Is a first call free?
What should I include in my message?
Can we start with email instead of a call?
Keep exploring
How we work
How we deliver software projects: discovery sprint, written specification, two-week sprints with demos, testing, launch, and support.
PricingPricing
Transparent, project-based pricing: a fixed-price discovery sprint, scoped implementation and build projects, and monthly support plans.
LabsLabs
Free interactive tools: estimate ERP ROI with a calculator, map a project's scope and open questions, and explore an AI document extraction review.
