Independent consultant
Direct, but fragile
The cost is lower. If that person drops out, your project stalls too.
Your operation grew faster than your systems. We design and build the software and automations that bring it up to speed, with Felipe leading an accountable team from start to finish.
Share your context
Three fields, two minutes, no newsletter. We reply within 1 business day to coordinate a 30 minute call.
- Timeline
- 4 to 8 weeks
- First step
- free call
- Ownership
- your code
From scattered data to a connected operation
Sound familiar?
- Month end close takes a week because someone consolidates six spreadsheets by hand.
- Your ERP, CRM and billing systems do not talk to each other. One person copies data between them.
- Monday’s decisions are made with last Thursday’s data.
- You already tried working with an independent consultant, and the project died when that person disappeared.
This is not a technology problem. It is the gap between how your business grew and the systems you use to run it. You pay for that gap every month in hours and errors.
Enough structure, without middlemen.
You work directly with a team that understands, designs and decides, with real delivery capacity.
Here · the middle ground
One accountable lead + team
Felipe leads design and decisions while a stable core team builds. Product and delivery stay under the team’s responsibility.
Agency
Structure, but distance
You speak with a salesperson. The person selling is not the person building your solution.
From understanding the operation to running it in production.
Three connected stages. The first call validates viability, and the assessment defines the project scope, timeline and value.
Technical operations assessment
A map of your processes and systems, a proposed architecture and a defined scope, timeline and value. The document is yours even if another team builds it.
Who: Felipe leads · the team documents
System in production
Working software, code and documentation you own, technical handoff and four weeks of support. Scope and value are defined in the assessment.
Who: Felipe directs product · the core team builds
Continuous improvement
Improvements, integrations, priority support and a quarterly roadmap. Available only for systems we built.
Who: The team delivers · Felipe prioritizes
Approximate equivalents at today’s rate · ExchangeRate API
We integrate AI where it improves a real operation.
We connect AI models to your data, systems and rules to solve concrete tasks with traceability, permissions and human escalation.
Chats and assistants
Assistants connected to company knowledge that answer questions, guide users and perform authorized actions.
Customer service
Request classification, initial responses, status checks and an orderly handoff to a person.
Internal teams
Document search, summaries, data extraction and decision support within the existing workflow.
Automation with control
Rules, validations and a record of every action so AI supports the operation without becoming a black box.
Experience across industries and borders.
We have delivered projects in Colombia, Mexico and Peru, adapting product, data and operations to regulated and demanding environments.
- Food industry
- Laboratories
- Healthcare
- Manufacturing
- Transportation
- Financial services
- Construction and civil works
- National government
Sample projects
- Laboratory · Colombia Manual consolidation of results → internal portal with sample traceability.
- Transportation · Mexico Dispatches coordinated over WhatsApp and Excel → operations board with alerts.
- Financial services · Peru Manual reconciliation between ERP and billing → integration with daily validations.
Commitments you can verify before delivery.
No anonymous metrics or numbers without context. These three conditions are visible from the start.
SignalHow to verifyState change
Scope
The assessment turns a vague operation into a proposal with clear boundaries, owners and decisions.
Before: open estimate
Now: defined scope + timeline
MAP · ARCHITECTURE · PROPOSAL Progress
You do not wait until delivery to discover what was built. You see the product working in the first or second week.
Before: status report
Now: working software every Friday
DEMO · BOARD · TESTING Ownership
Continuity does not depend on a black box. Repositories, access, documentation and context stay with you from day one.
Before: dependency
Now: your code, day 1
CODE · DOCUMENTATION · HANDOFF Sound like your operation?
Tell us about the process causing the most friction and we will tell you whether it is viable.
You will know where your project stands every week.
The sequence does not end with a presentation. It ends in production, ownership and a technical handoff.
- 01
weeks 1 and 2
Diagnosis
Interviews, systems map and a defined scope, timeline and value.
- 02
week 1 or 2
First working version
A navigable version of the critical flow. From then on, you see working software every Friday, not slides.
- 03
visible cadence
Every week
A progress demonstration, a shared board and an open testing environment.
- 04
production
Delivery
Code, documentation, technical handoff and four weeks of support.
- Weeks 1 and 2
- Diagnosis. The team begins the assessment and presents the first demonstration in week 1 or 2.
- Weeks 3 to 8
- Build and delivery. The core engineering team builds and demonstrates working software every Friday.
- When needed
- Specialists. The specialist network joins only for a specific capability.
The team stays involved throughout the project. Core engineering joins during the build, and specialists participate when the scope requires them. From the first demonstration onward, you see working software every Friday.
Technology project and product leadership
Felipe leads; the team takes the solution to production.
Felipe has more than 8 years leading technology projects as a project manager and product manager. The largest initiative he has led had a budget above COP 5 billion.
Felipe leads the assessment, product decisions and project management. A core engineering team builds, while specialists join when the scope requires them. In the proposal, every person appears with a name, a role and a start date.
Verify it on LinkedInDirect questions.
-
The first call is free: that is where we determine whether the project is viable. If we move forward, the assessment costs between COP 600,000 and COP 1,000,000 depending on the project. The result is yours whether you build with us or with another team: a process map, an architecture and a proposal with scope, timeline and value.
-
The document is yours: the map, the architecture and the proposal are useful even if another team builds. And if we build together, the assessment is credited toward the project value.
-
Felipe leads design, decisions and project management. A stable core team builds each module and every delivery is reviewed by the team.
-
Usually 4 to 8 weeks in total, including the assessment. The timeline is committed in the proposal, not left as an open estimate.
-
No. Felipe remains your point of contact and project lead. The person who understands the problem decides together with the team that builds, with no middlemen.
-
Just three things: which process hurts the most, which systems are involved and who operates it. No technical documentation needed.
-
You do. Repositories, documentation and access are in your name from day one.
-
It depends on scope. Your proposal names each person, their role and when they join. There is no anonymous capacity.
-
A shared board, documentation and at least one other person with context reduce that dependency. Felipe remains contractually accountable and the team preserves operational continuity.
How many hours did the gap between your operation and your systems cost this week?
On the first call, we review the process causing the most friction and determine viability. If there is a fit, the assessment defines the project scope and value.
Write to us
Share your context
Three fields. No newsletter or automated sequences.