The answers people ask us for before they write.

With a conversation, not a proposal. You write, we reply within one business day, and the first call is spent on the business: objectives, users, constraints and the technology already in place. What comes out of that is a scope with a price, not an estimate with an asterisk.

Five phases, and the fifth loops back to the first. Understand the business. Design the architecture and the roadmap. Build, iterating as we go. Deploy to production with quality, security and performance in mind. Evolve as the business changes — and every shift in the business reopens the cycle where it began.

It depends on the scope and on the state of what already exists, and any number given before looking at both is a guess. Turning it into a date is what the first phase is for; what we commit to before that is the scope of that phase.

Within one business day, to every enquiry. That is not a target we publish and hope for — it is the commitment on the contact page.

Six capabilities: AI and intelligent automation, custom software development, data and analytics, cloud and DevOps, enterprise systems and integrations, and quality engineering. Each one has its own page with what it covers in detail.

The concrete list is AI assistants and conversational AI, AI agents, intelligent process automation, AI contact centre, AI integrations, and workflow automation. If a problem is better solved without a model, we say so — that is also what the first phase is for.

Yes, and it is the normal case. System and API integration and legacy application modernisation are part of enterprise systems, and the usual answer to a fragmented stack is to move what is costing money and connect what is working.

Yes. Custom software covers web applications and digital platforms, mobile apps, desktop applications, e-commerce, and custom enterprise platforms.

Quality engineering is one of the six capabilities, not a step someone remembers at the end: QA, software testing, test automation and performance testing.

By the problem, not by the technology. The solutions pages are framed by business challenge — automating a process, modernising something legacy, getting decisions out of your data — and each one says which capabilities it combines.

Yes, as a partner registered with the vendor. We implement and customise it, integrate it with the systems you keep, migrate you off spreadsheets and legacy systems, and support, host and license it afterwards. The Odoo page answers the specific questions — Community or Enterprise, what happens to your data, who maintains it.

No. Legacy application modernisation and system integration are part of enterprise systems, and replacing a system nobody complains about is paying twice for the same thing. Sometimes the right answer is to connect what you have, not to change it.

There is no published rate, because the price is moved by three things: the scope, the state of what already exists, and the deadline. What we commit to before any project is the scope of the first phase — and the price of the project comes out of that phase, closed, before anyone builds anything.

Three ways. Fixed price against a closed scope, when the scope can be closed. Time and materials, when it genuinely cannot — discovery work, or a system nobody has mapped yet. And a monthly retainer, for ongoing support, evolution or reserved capacity.

Fixed price if the scope can be closed: you get certainty and we carry the estimate risk. Time and materials if the work is discovery, where a fixed price is only a fixed price because someone padded it. A retainer if what you need is continuous capacity rather than a project. We decide it with the scope in front of us, not before.

You do. The intellectual property (IP) of the development is the client's.

Yes, before we see anything about your business. A first conversation about an operation usually means looking at how a company actually makes money, and that is not something you should have to hand over on trust.

In your infrastructure when you have it — your repositories, your cloud, your access — and in ours when that is what the project needs. If it runs on ours, the server cost comes at a discount.

No. Working inside the client's own repositories, cloud accounts and access is the default, precisely so that nothing we build ends up living somewhere you cannot reach.

One of three things, and it gets chosen before the end rather than after it: a documented handover so your own team runs it, a continuous support agreement with us, or hosting and operation managed by us.

Yes. Delivery includes a warranty period in which fixing what we delivered is not billed. The exact term is set in the project contract — it depends on the scope, so a single number on a web page would be either wrong or meaningless.

Yes: hosting, backups, monitoring and updates. On our infrastructure the server cost comes at a discount, and the support agreement covers the operation rather than only the incidents.

Then it is handed over documented, and that is the end of the dependency. The code is yours, it lives in your repositories, and the handover is a phase of the project rather than a favour afterwards.

We work with representation in the United States and Colombia, and with clients across the United States, Spain and Colombia. That model is deliberate: it lets us combine specialised talent and collaborate across markets and time zones.

The reference workday is 9:00 to 18:00 in each local time. The United States and Colombia are both at UTC−5 — Colombia does not observe daylight saving — and Spain sits at UTC+1, which leaves a real block of shared hours with every one of the three. The home page draws the overlap.

Spanish and English. This entire site exists in both, and so do the conversations, the documentation and the handover.

It is used to answer you. We keep an enquiry for as long as it takes to answer it and to carry on the conversation it started, and in any case no longer than 24 months after the last exchange, at which point it is deleted or anonymised.

No. It sets no cookies of its own and stores nothing in your browser — no analytics, no advertising or remarketing tags, no tracking pixels, no social embeds, no chat widget. The fonts and the videos are served from our own domain rather than a third party, so loading a page here does not announce your visit to anyone. Our hosting provider may set a strictly necessary security cookie, which does not identify you.

Yes. You can ask for a copy of it, for it to be corrected, deleted or restricted, and the privacy policy says exactly how and to whom.