Start with a conversation, not a pitch.
We design for clarity, not noise. Before we touch a pixel, we need to understand your business context. This page is your entry point to that dialogue.
What to prepare for our call
- Business constraint: What's the one metric you need to move? (Revenue, conversion, user retention)
- Audience friction: Where are users dropping off or getting confused right now?
- Timeline reality: Your desired launch date. We'll tell you if it's achievable.
- Brand assets: Logo files, guidelines, or a "do-not-use" list.
Outcome: A written scope and fixed-price proposal delivered within 48 hours of our call.
Studio Entrance
El Poblado, Medellín. Our home base for deep work and focused collaboration.
Point of Contact
For Initial Inquiries
Use this for project proposals, RFPs, or partnership questions.
[email protected]For Active Projects
Dedicated channel for clients in progress. Response within 2 business hours.
+57 604 444 3543Studio Hours
Monday – Friday
9:00 AM – 6:00 PM (GMT-5, Medellín)
We observe local Colombian holidays.
Location & Context
Our studio is rooted in Medellín, Colombia, but we operate on a hybrid model. We frequently work with clients in North America (EST alignment) and Europe (CET alignment).
nodexo
Calle 10D #30A-115, Int 201
Medellín, Colombia
Visits by appointment only.
Pitfalls to Avoid
A short list of common miscommunications that slow down the process.
Vague Briefs
"We need a new website" is a starting point, not a brief. We need the *why* behind it. Prepare to discuss the business case.
Ambiguous Budgets
Stating "flexible budget" often leads to mismatched expectations. Be honest about constraints; we can design within them.
Skipping Discovery
Wanting to jump straight to "make it look like this" skips the work of ensuring it solves your actual problem. Trust the process.
Start Your Project Proposal
Tell us about your project. We review every inquiry personally and respond within 24 hours.
Lexicon
How we talk about the work. These terms frame our collaboration.
Constraint Mapping
We start by diagramming your hard limits (time, budget, tech) before brainstorming solutions. A solution that violates a core constraint isn't a solution.
Artifacts, Not Just Mockups
We ship assets you can use: component libraries, design tokens, and annotated specs—not just final screenshots. This ensures the work endures.
The 80% Rule
We design for the 80% use case first. Edge cases are planned for, but we don't let perfect versatility derail a strong, focused core experience.
The Handoff is a Guide
We don't just "hand off files." We provide a short walkthrough of the asset library and a documented rationale for key decisions.
Clarity > Cleverness
If a clever interaction requires a tutorial, we've failed. The goal is intuitive use, not showcasing interaction patterns.
Stakeholder Alignment
We design for the decision-maker, but build for the end-user. Every major deliverable is reviewed with both perspectives in mind.
Our Evaluation Method
We assess project robustness using three lenses, not vanity metrics. A "strong" design is one that passes this simple checklist.
1. Constraint Adherence
Does the solution respect the core, non-negotiable limits (budget, timeline, technical stack)? A brilliant idea that breaks the budget is not a viable path.
2. User Priority Map
Can we trace a direct line from the user's top priority to the primary interface action? No dead ends. No decorative features.
3. Maintenance Reality
Will this system be maintainable by a team without our direct involvement? We provide the guide, not just the destination.