01
We work in the open, not in black boxes.
You have access to the repository, the project board, and the decision log from the first sprint. There's no curtain: there's a process you can open and review as it moves, without asking permission.
How we work
Six steps, the same on every project. We didn't design them to sell: they come from years of shipping software on teams where improvising wasn't an option. Today they sustain production systems that run real businesses every day, and they're exactly what will happen with your project, with what you receive at each step in writing.
PRINCIPLES · WHAT GUIDES US
Three principles that shape every engagement.
02
Big decisions happen early.
Technical architecture, brand direction, and scope are settled in writing before we build. Mid-project changes are rare because the heavy thinking happens upfront, and when they do occur, they're documented and approved before execution.
03
We leave you better than we found you.
At the end you keep the documentation, code, files, and training, all in your name. If you continue with us, it's by choice. If you continue with another team, they have everything they need to take over without calling us.
THE SIX STEPS · IN DETAIL
The six steps, in detail.
- DISCOVERY CALL
30 MIN · FREE · NO COMMITMENTA conversation, not a sales presentation.
You describe the actual pain (operational, brand, digital presence) and what you've tried. We share how we've solved similar problems and what we think would work for yours. You talk directly with the person who designs the strategy and the person who builds the system, not an account executive.
By the end of the call, you know whether it makes sense to continue. We do too. If your need is better served by a SaaS, a freelancer, or another team, we tell you on that same call, with references ready when we have them.
WHAT YOU GET- 30 minutes with the two people who would make the decisions on your project
- An honest read on technical and strategic fit, including a "we're not the right option" if that applies
- If we proceed: a committed date for receiving the proposal
- DIAGNOSIS AND PROPOSAL
5–7 BUSINESS DAYSThe essentials in writing, so you can decide with confidence.
After the call, we write a proposal with the project's essentials: the objective, phase-level scope, estimated timelines, and investment. It's what you need to decide: clear, signable, no fine print. The deep analysis (deliverables named one by one, integrations, data model, risks, and assumptions) is developed once the agreement is signed, as the project's first deliverable: that way it's done with your full context and can be adjusted along the way for the project's success.
The proposal is signable as written. If you want adjustments, we iterate once before signing, not after.
WHAT YOU GET- A proposal document with objective, phases, estimated timelines, and investment
- Once signed: the detailed analysis as the project's first deliverable
- A 30-minute meeting to review the proposal line by line
- KICKOFF AND PLANNING
1 WEEKAccess to everything, clear calendar, your role defined.
Once the agreement is signed, we start with the detailed analysis (deliverables named one by one, integrations, data model, risks, and assumptions) and turn it into the sprint or phase plan with milestones and dates. We open access to the repository, the board, and the documentation, and the decision log is open from day one. Every scope, design, or architecture decision is written down, with date and owner.
By the end of the week, you have access to everything, you know what happens when, and you understand your role in the process. Because yes, you have one, and it isn't answering messages at 1 AM.
WHAT YOU GET- The detailed analysis with every deliverable named, what isn't written there isn't in scope, and what is, gets delivered
- A project plan with milestones, dates, and meetings already on the calendar
- Access with your own user to the repository, the board, and the documentation, not screenshots: access
- The project's decision log, open and visible to you from day one
- EXECUTION BY SPRINTS OR PHASES
VARIES BY SCOPEThe actual work, visible as it happens.
From the first demo, you have a staging environment with its own URL: the same code that will go to production, running on test data, open for you to review whenever you want without asking us. Each brand phase closes with real visual deliverables you approve before we continue. Demos are about working output, not slides.
Scope changes, when they happen, are documented and approved before execution. They don't show up on the final invoice as a surprise. This same cycle is what keeps Chiquicuidados' appointment booking and e-invoicing system in production today.
WHAT YOU GET- A staging environment with your own URL from the first demo (software projects)
- A demo or review at the close of each sprint, on the date set at kickoff
- Every scope change in writing and approved by you before execution
- Responses within 3 business hours during the workday
- DELIVERY AND TRAINING
1–2 WEEKSFull handoff. We don't disappear.
You receive architecture documentation that explains why the system is built the way it is, not just what it does: it's the document another team would read to take over without calling us. For brand projects, the complete brand book with source files.
And a training session covering every role that uses the system, operations manager, accountant, salesperson, receptionist, whoever. Nobody is left not understanding the system because "that module wasn't for me."
WHAT YOU GET- Architecture documentation that explains the why of the system, not just the what
- Complete brand book with source files (when applicable)
- Training session (1–2 hours base) covering every role on your team
- Repository, credentials, and access transferred to your name, not shared: transferred
- POST-DELIVERY SUPPORT
30 DAYS INCLUDED · OPTIONAL RETAINERHow the backing works, concretely.
For the first 30 days after delivery, any bug, minor adjustment, or question is handled at no additional cost, through the project's same direct channel and with the same person who built your system. It's time for your team to adopt it with confidence and for anything not covered in the original scope to get resolved.
Day 31 holds no surprise. If you want continuity, the monthly retainer is agreed in writing: dedicated hours per month, defined scope, no trap clauses. It's optional and we don't pressure. If you don't take it, you already have everything you need to operate without us. That was the point of step 05.
WHAT YOU GET- 30 days of included support, with the same channel and the same person from the project
- Bugs, minor adjustments, and questions handled at no cost during the period
- Optional retainer with hours and scope in writing, or a clean exit, no dependency
COMMITMENTS · HOW WE BACK THEM
Four commitments that back every engagement.
01
30 days of support included after delivery.
The real fear of hiring a project like this is paying and being left alone. That's why post-delivery support isn't an add-on: it's included in every project, in writing, in the proposal.
In practice: For 30 days, bugs, adjustments, and questions are handled at no cost, with the person who built your system, not a help desk.
02
Written proposal before anything starts.
Objective, phase-level scope, timelines, and investment in writing and signed. The full detail is developed as the project's first deliverable, and changes are documented and approved before execution.
In practice: The final invoice has the same numbers as the signed proposal, plus approved changes, clearly identified.
03
Documentation, code, and files are yours.
At delivery, everything is in your name: repository, source code, infrastructure, design files, brand book, training. No post-delivery dependency.
In practice: If you continue with another team, they have everything they need. If you continue with us, it's because you want to, not because you have no alternative.
04
Under 3 business hours response time.
Direct communication with the people who decide and build, no intermediaries, in Spanish or English.
In practice: Your Monday 10 AM message has a response before 1 PM. Our business hours are 9 AM–6 PM El Salvador time.
TOOLS · CADENCE
Tools and cadence.
This is our default stack: just one. If your team already works with its own standard, we adapt, and that adaptation is documented at kickoff, not improvised.
TOOLS
- Decisions don't live in a chatEvery scope, design, or architecture decision is logged in Notion, with date and owner. What's agreed doesn't depend on anyone's memory.
- The code has history and controlGitHub. Version control from the first commit. Every change is logged, dated, and traceable.
- Design happens in the openFigma. Working files shared with you, not loose exports.
- The real status is visibleLinear. The project board, open to you at all times.
- Demos are about real workGoogle Meet, scheduled from kickoff, about working software or deliverables.
- Daily conversation flowsSlack or WhatsApp Business, for conversation, not decisions. What's agreed in chat moves to the decision log within the next business day.
TYPICAL CADENCE
- Mon – FriOpen async channel. Responses within 3 business hours, 9 AM – 6 PM.
- Per sprintDemo or review (~30–45 min on Google Meet) on the date set at kickoff, plus a short retro: what worked, what to adjust.
- MilestonesFormal review with documented decision before advancing.
THE CONVERSATION
Does this sound like the way to work on your project?
If this is how you'd want your engagement run, book the discovery call. If you're not sure how it applies to your specific case, also book it. That's what the call is for. It's 30 minutes, and the person on the other side is the same one who would be on your project start to finish, including the 30 days after delivery.