A Method, Not a Process.
Our approach is built for deep collaboration, not transactional delivery. We don’t just build websites; we document a journey from ambiguity to clarity, with you as the co-author.
Project At-a-Glance
- Initial Phase 14 Days
- Core Team 1:1 Direct
- Communication Single Channel
- Post-Launch 30-Day Care
The Medellín Method
Our studio is born from a specific context. Medellín isn't just an address; it's a proof of concept for reinvention. We apply that same ethos to our work: starting from raw materials and building something resilient, elegant, and purposeful. This means we reject the agency assembly line. Every team member—from strategists to developers—engages with the full project lifecycle, ensuring continuity and deep context.
This is why we frame our clients as co-authors. You provide the narrative; we provide the craft. Communication isn't layered through account managers; it's direct, happening in a single shared workspace. This eliminates the telephone game and ensures decisions are made with full transparency.
"We don't have projects. We have partnerships. The tool is the web; the outcome is a shared success story."
The 5-Stage Build Cycle
A project at nodexo moves through a deliberate sequence. Each stage has a clear input, process, and output.
Discovery & Alignment
We document the 'why.' Stakeholder interviews, success metrics, and the creation of an 'anti-brief'—what we explicitly will not build.
Architecture & Systems
The blueprint. Sitemaps, content hierarchies, and technical constraints are mapped. No code yet—just logic.
Visual Translation
From wireframes to high-fidelity screens. This is where the brand's visual language is fully realized.
Prototyping & Motion
Interaction logic and micro-animations are defined and tested. We validate flow, not just pixels.
Launch & Handoff
Deployment, 30-day hypercare, and a complete document package for future scaling.
Visual Translation: From Concept to Code
Hover over the stages to reveal the underlying sketch layers.
The First 14 Days: A Scenario
The Kickoff Sprint
We grant full Figma/Notion access. We interview key stakeholders not about features, but about business outcomes and pain points. We audit every existing asset.
The Anti-Brief
We analyze the competitive landscape not for imitation, but for differentiation. We then draft the 'Anti-Brief'—a one-pager defining what our final product will explicitly NOT be.
Blueprint & First Concepts
Low-fidelity wireframes are built and approved. Technical feasibility is confirmed. We then present three distinct visual directions—each rooted in the strategy, not arbitrary style.
"By Day 14, the founder of a SaaS startup saw three website concepts that solved their core trust problem—each with a distinct path. They didn't just see pixels; they saw a translation of their investor pitch into a user experience. The anti-brief meant we spent zero time discussing features they didn't need."
Constraint Respected: 6-week total timeline from kickoff to launch.
Trade-off Made: Speed vs. Depth. We chose depth in the first 2 weeks to avoid rework later.
The Framework Boundaries
- Client provides clear business objectives.
- Decision makers are available for bi-weekly reviews.
- Content inputs are available when needed.
A 6-week timeline becomes 8-10 if stakeholders are not aligned or assets are incomplete. We build on your time, not ours.
Method Note
This framework is evaluated on two axes: robustness (does it handle changing requirements?) and risk (where are dependencies?). The "Anti-Brief" stage is our highest-risk mitigation tool, adding clarity before visual work begins.
Common Pitfalls & How We Avoid Them
The client keeps adding "just one more thing" without timeline impact assessment.
Our Fix: We maintain a visible "Scope Log" in Notion. Every new request is tagged with a time/cost estimate for the next review.
Development is opaque, with no previews until the end.
Our Fix: Weekly Staging Deployments. You see a live, updated preview every Friday, even if it's just the header on a new page.
Agency disappears after launch, leaving clients to manage breakages.
Our Fix: The 30-Day Hypercare Period is a fixed part of our contract. No extra cost for bug fixes.
Finish Well: The 30-Day Hypercare
Launch is not the finish line. The first month is critical for user adoption and technical stabilization. Our post-launch package ensures your investment delivers value from day one.
- ✓ Bug Swatting: Immediate fixes for any code errors or browser inconsistencies.
- ✓ Analytics Review: A collaborative review of first-week user data to identify friction points.
- ✓ CMS Training: A recorded walkthrough for your team, tailored to the specific tools they will use.
- ✓ Future-Proof Guide: Documentation on how to scale content and features without breaking the design system.
Our process is designed for partnership, not service delivery. We prioritize clarity over speed in the early stages to build a resilient foundation.
This framework requires an engaged client, direct communication, and a shared commitment to the defined outcomes.
The result is not just a delivered product, but a documented journey and a sustainable system for growth.
No obligation. We'll respond within 1 business day.
nodexo — Medellín, Colombia
Start a conversation · [email protected] · +57 604 444 3543