1-2 weeks
Process analysis
We map the real flow with the people who work it every day: inputs, outputs, exceptions, bottlenecks. The deliverable is a specification you understand too — not just us.
Software development & integration
We build only what's needed, starting from your process — not from the technology.
Custom applications, integrations between the systems you already use, automations and tailored Odoo modules. We hand over code, documentation and autonomy: the software stays yours.
Bespoke software is an application or feature developed to meet a specific need in your business. Gitogi starts with your process, assesses whether new software is worthwhile and builds only what is needed. The code and documentation stay with you.
Four ways we turn technology into a tool that serves your work, not a burden.
Internal tools, portals and management apps built on your real process, when off-the-shelf software isn't enough.
We connect your systems — Odoo, management software, e-commerce, external services — so data flows on its own, with no manual re-keying.
We turn repetitive tasks and document flows into reliable automations, freeing time for what creates value.
We tailor Odoo where your business is different, keeping the system upgradable and coherent.
How we work
No blind quotes: first we understand the process, then we write the code.
1-2 weeks
We map the real flow with the people who work it every day: inputs, outputs, exceptions, bottlenecks. The deliverable is a specification you understand too — not just us.
2-4 weeks
A first usable version of the most important flow. You try it with real data and we correct course before building the rest.
4-8 weeks
We build the rest in iterations, integrating the systems you already use (ERP, e-mail, spreadsheets). Frequent releases — you never lose sight of the work.
1 week
Team training, documentation and code you own. Maintenance if you want it — not because you're locked in.
Transparency about limits is part of the method — here are ours.
If an Odoo module or a standard tool solves it, we use it. We write code only when it adds real value.
First we understand the process and the expected value. Technology comes after, never before.
We hand over code, documentation and skills. The software is yours, and you stay free to evolve it with whoever you want.
Custom software extends the ERP where needed, without breaking the single system where your company's information lives.
Discover OdooWe bring AI inside the tools we build, where it truly adds value — governed and compliant.
Discover AI integrationfrom the field
On-site server support is ending. We plan cloud migration around acceptable downtime, tested recovery and a documented way out before you commit to a provider.
Read the scenario Cross-sector · Inherited softwareRepresentative scenario: how we take on inherited software, find out what keeps it running and assess whether to change it or keep it as it is.
Read the scenario Service businesses · Disconnected systemsA representative scenario for service businesses: conflicting records, manual transfers and silent failures. How we agree which data to trust and check that it reaches its destination.
Read the scenario Manufacturing · In-house business applicationsA representative manufacturing scenario: rebuild a legacy application in stages, document its business rules first, keep old and new running together and test a way back for each part.
Read the scenarioFrequently asked questions
Off-the-shelf software makes sense when it supports the process you need to manage. Bespoke software is worth considering when a specific need remains unmet, which may mean building just one feature. Gitogi starts with your process to assess whether new software is needed at all.
FAQ 01 / 6
There is no standard timeline: it depends on what the software needs to do and which integrations it requires. A useful estimate needs a clear picture of who will use it, the tasks they need to complete and the systems it must exchange data with. Gitogi's free introductory call covers your process, the expected value and feasibility.
FAQ 02 / 6
Yes, the code and documentation stay with you. You can make them available to whoever takes on the software's maintenance and further development.
FAQ 03 / 6
Responsibility for maintenance needs to be agreed during the project, based on the skills and resources available. The code and documentation stay with you for whoever takes the work forward. Gitogi's AIRA method aims to give you the independence to do that.
FAQ 04 / 6
That depends on the connections your existing systems support and the data they need to exchange. Before defining the development work, you need to establish which information should move between systems and where it should be kept up to date.
FAQ 05 / 6
Your process and the expected business value determine what is worth building. Gitogi's free introductory call explores both, alongside feasibility. The advice may be that developing new software is not worthwhile.
FAQ 06 / 6
We start with a free call to understand the process, the expected value and feasibility. No commitment, with an honest opinion on what's really worth building.
Book a free call