Predictable projects, written commitments
What a project with TQ Innovate looks like, what you receive at each stage, and the terms that protect you.
Three phases, each closing with something you can hold
No phase ends on a promise. Each one produces a deliverable you review and accept.
1 · Define
We sit with your team and map how the work is done today, not how a manual says it should be.
You receive: a written scope, the integration list, the project schedule and a fixed price.
2 · Build
Development against the signed scope, with a working demonstration at the close of every month.
You receive: a running system in a test environment from the first month, and access to the repository.
3 · Operate
Go-live, training for your team, and the support arrangement that keeps the system healthy.
You receive: the platform in production, documentation, training sessions and a closing report.
What stays with you when the project ends
Source code
Delivered complete to your repository. What we build for your business belongs to your business.
Two environments
Production and a separate test environment, so changes are validated before they touch real data.
Documentation
Installation guide, operations manual and the technical detail of every integration built.
Training
Separate sessions for the technical team and for the administrators who run the system day to day.
Administration panel
So your team changes parameters, users and catalogues without depending on us for routine work.
Test record
The list of tests executed and their results, signed at closing. Useful the day an auditor asks.
The questions buyers ask before signing
Answered here, so the first meeting can be about your business instead.
Who owns the development?
You do. The modules built for your business are your property, with a perpetual licence over the platform they run on. There is no lock-in and no hostage code.
Is it compliant with the tax authority?
Tax documents follow the official schemas of the Ministry of Finance of El Salvador, with digital signature and the official acknowledgement stored for every document issued.
How is our data protected?
Encrypted credentials that are never stored in readable form, two-step verification, separated environments, and an audit trail recording who did what and when.
What if the service fails?
Tested backups, permanent monitoring, a named contact and agreed response times. After an incident you receive a written account of what happened.
What if we stop working together?
You keep the source code, the documentation and the environments. We hand over to whoever continues, without drama and without withholding anything.
Is our information confidential?
Confidentiality agreements are signed before the first meeting where real data is discussed, and they bind both parties.
Warranty and support
A system goes into production and then real life begins. What follows is agreed before it starts, not improvised when something breaks.
Warranty included
Sixty days from delivery covering defects in the work delivered, at no additional cost.
Maintenance plan
Optional afterwards: incident handling, platform updates and an hour bank for minor changes.
Let us talk about your project
Book a meeting and we will show you the system working on a real case, not on slides.
Request a meeting