Skip to main content
FAQ

Questions we hear a lot, answered without the sales voice.

Can't find what you need? Email us. A real engineer will reply.

About working with us

We're a young engineering company. These answers cover the questions we hear most, about how we work, what we cost, and what happens after launch. If yours isn't here, ask us directly; an engineer will reply.

Didn't find your question?

The questions above come from real conversations, but every project has its own. If yours isn't here, send it through the contact form or by email and we'll answer it directly, within 12 business hours.

For deeper reading, our articles cover the most common decisions in detail, from planning an ERP migration to choosing between retrieval and fine-tuning for AI.

Frequently asked questions

How long does an Odoo ERP implementation take?
Typically several weeks to a few months depending on modules, data migration, and integrations. You get a specific timeline after the discovery sprint.
Do you support Odoo Community and Enterprise?
Yes. We recommend Enterprise for teams needing its extra apps and vendor support, and Community for teams with technical capacity who want full control.
Can you integrate Odoo with our existing tools?
Almost certainly: ecommerce platforms, CRMs, accounting tools, payment providers, logistics APIs, and legacy systems.
What does your AI development process look like?
A short discovery to define the problem, success metrics, and data, then a prototype evaluated on your real data before any production rollout.
Do you offer post-launch support?
Yes. Projects include a 30-day hypercare period, followed by optional monthly support plans.
How do you handle data migration?
As its own project phase: audit, clean, map, rehearse, and validate with your team before the final cutover.
Is our data secure during the project?
We work under NDA from day one, use encrypted infrastructure, apply least-privilege access, and will review your security addendum.
Can you work with our internal team?
Yes. We can lead, augment, or advise, whatever fits your team.
Which industries do you work with?
Logistics, retail and ecommerce, manufacturing, real estate and construction, financial services, agritech, and professional services, among others.
Who owns the code you write?
Client-funded custom work belongs to you after payment. We keep ownership of pre-existing tools and reusable components.
Do you work remotely?
Yes, with on-site workshops when they add value, such as discovery or training.
How do we get started?
Email us with a short description of the problem. We'll schedule a 30-minute discovery call to see if we're a fit.
How big is your team?
Deliberately small and senior. We bring in trusted specialists for specific needs, and we'll always tell you who is working on your project.
You're a startup. What happens if you disappear?
Your system doesn't depend on us: code lives in your repository, accounts are in your name, and documentation and runbooks are handed over, so any competent team can continue.
Do you take on small projects?
Yes. Many engagements start with a small, well-defined piece of work, such as one integration or one module, and grow from there.
Can we talk to the engineers before signing?
Yes. The engineers who would work on your project join the discovery call and the sprint itself.
Do you sign NDAs?
Yes, a mutual NDA before discovery if you'd like one.
What time zones do you work in?
We work remotely with clients across time zones and agree overlap hours for calls and support at the start of each project.
Do you work with other agencies or freelancers?
Yes. We can collaborate with your existing partners or bring in specialists, with clear ownership of each part.
How do you handle changes in scope?
Changes are discussed openly, written down with their effect on cost and timing, and agreed before work continues.
Do you offer a free consultation?
Yes. The first 30-minute call is free and comes with no obligation.
Can you rescue a project another partner started?
Often, yes. We start with a review of the code, data, and setup, then agree a plan to stabilize and continue.
Do you sign NDAs before a first call?
Yes, if you'd like one. For most first conversations a high-level description is enough, and we treat everything you share as confidential either way.
Can you review a proposal from another vendor?
Yes. A second opinion on scope, architecture, or estimates is a common and useful starting point, and we'll be candid even if the other proposal is good.
Do you offer training for our team?
Yes. Handover always includes documentation and walkthroughs, and we offer role-based training for ERP users and technical handover sessions for developers.
What happens if we want to stop mid-project?
You keep everything built and documented up to that point. Phased plans exist partly so that stopping after any phase still leaves you with something useful.
Do you work with companies outside your time zone?
Yes. We agree overlapping hours for calls and demos, and keep the rest of the communication written so nothing depends on being online at the same time.
How do you price small changes after launch?
Through a support plan with included hours, or as small fixed-price change requests if you don't need ongoing support.
Can you take over a project another partner started?
Yes. We start with a short review of the code, infrastructure, and documentation, then give you an honest assessment and a plan before taking responsibility.