00Services
Services
Six lines of work for companies that need to build, run or review a digital platform. Each one says what is included, what is not and what you receive at the end.
Summary
- Service lines
- 06
- Engagement models
- 03
- Base deliverables
- 04
- How it starts
- A 1–2 week diagnosis
What we do
Six service lines. Many projects combine several, and we help you sort them out.
Shape of Web and digital platforms: Open, regular surface: a stable base your team publishes on.
Select a line to see it on the card.
- Corporate sites, landing pages and admin panels your team can edit on its own, with the domain and the code in your name.
Includes, for example:
- Corporate sites
- Admin panels
- CMS-style editable sections
See Web and digital platforms in detail
- We turn one of your business processes into a web application: interface, API, database, users and permissions.
Includes, for example:
- Web applications
- APIs
- Dashboards
- Automated deployments, monitoring and runbooks, so your team can ship and recover the system without us.
Includes, for example:
- Cloud deployment
- CI/CD pipelines
- Monitoring
- Language model workflows connected to your data, with a quality evaluation and an estimate of what they cost to run.
Includes, for example:
- LLM workflows
- Knowledge bases
- Internal copilots
- We review a platform you inherited or are moving to a new vendor: ranked findings, access cleaned up and a fix plan.
Includes, for example:
- Vulnerability review
- Access and permission hygiene
- Technical handover
- A written diagnosis, roadmap and estimate, before you commit budget.
Includes, for example:
- Technical diagnosis
- Roadmaps
- Transition between vendors
How to engage us
We don’t publish prices: they depend on the scope. Response times, where they apply, are set in the contract.
| Criterion | AFixed-scope projectTell us about your project: Fixed-scope project | BMaintenance and operations retainerTell us about your project: Maintenance and operations retainer | CBlock of hoursTell us about your project: Block of hours |
|---|---|---|---|
| When it is useful | When the goal and its limits are clear. | When something that already works needs ongoing care. | When the work is occasional or variable. |
| How it works | Scope, exclusions, milestones and price agreed in writing before work starts. | A monthly fee to maintain and improve platforms in production, with an SLA agreed in writing. | Prepaid hours you use task by task, with a log of what was used. |
| What you receive | The deliverables in the proposal and the handover record at the close. | Corrective and evolutionary maintenance, a periodic report and up-to-date documentation. | The hours log and the documentation for each task. |
| Contract terms | Price and schedule are set in the proposal. Scope changes are quoted separately. | The monthly scope and the SLA are agreed in writing in the contract. | How long the hours stay valid, and on what terms, is set in writing. |
- A
Fixed-scope project
- When it is useful
- When the goal and its limits are clear.
- How it works
- Scope, exclusions, milestones and price agreed in writing before work starts.
- What you receive
- The deliverables in the proposal and the handover record at the close.
- Contract terms
- Price and schedule are set in the proposal. Scope changes are quoted separately.
- B
Maintenance and operations retainer
- When it is useful
- When something that already works needs ongoing care.
- How it works
- A monthly fee to maintain and improve platforms in production, with an SLA agreed in writing.
- What you receive
- Corrective and evolutionary maintenance, a periodic report and up-to-date documentation.
- Contract terms
- The monthly scope and the SLA are agreed in writing in the contract.
- C
Block of hours
- When it is useful
- When the work is occasional or variable.
- How it works
- Prepaid hours you use task by task, with a log of what was used.
- What you receive
- The hours log and the documentation for each task.
- Contract terms
- How long the hours stay valid, and on what terms, is set in writing.
In all three models
- Third-party costs are quoted separately and go in your company’s name.
- We can sign NDAs and intellectual property agreements covering the deliverables.
- We issue CFDI 4.0 electronic invoices, the Mexican standard.
03Questions
Frequently asked questions
What people ask us most before starting.
Yes. When the project closes, the source code, the documentation, the access and the infrastructure pass to your company. The exact ownership terms are set in each project’s contract.
Your company does, in its own name. Hosting, domains, licences and other third-party services are quoted separately.
Yes. The maintenance and operations retainer covers corrective and evolutionary maintenance, with an SLA agreed in writing. For occasional needs, there is the block of hours.
Yes. We can sign a confidentiality agreement and intellectual property agreements covering the deliverables.
We issue CFDI 4.0 electronic invoices, the Mexican standard.
With a diagnosis: we look at your goal, what already exists and its risks. Then we send you a proposal with the scope, exclusions, milestones and cost. The diagnosis is paid, and if you go ahead with the project its fee is credited against the proposal.
Usually Next.js, React and TypeScript. We deploy on Vercel and keep the code on GitHub. We pick the technology for the problem and write it into the proposal.
It depends on the scope: after the diagnosis we send a proposal with the scope, timeline and cost.
04Next step
Not sure which line fits?
Online scheduling is not available yet.
Several lines at once
Many projects combine several. Tell us what you need and we will help you sort it out. For now the contact form is a demonstration: nothing is sent or stored.