--- title: "How Ramón Chancay works" description: "What an engagement is like week to week: direct communication, a weekly meeting with a demo, a delivery every Friday and a shared schedule." author: Ramón Chancay lang: en canonical: https://www.ramonchancay.me/how-i-work --- # How Ramón Chancay works What an engagement is like week to week: direct communication, a weekly meeting with a demo, a delivery every Friday and a shared schedule. ## Four habits, the same week, every week. What keeps a project on track is not the stack. It is the rhythm. ### One direct channel, nobody in between. You have my WhatsApp, or a Slack channel with you and your team. You ask, you decide, and I answer the same day, in your language. Every important decision is written down in a shared document, so nobody has to remember what was said on a call. - Same-day replies, Monday to Friday - Decisions in writing, not in anyone’s memory - English or Spanish, whichever your team prefers ### One fixed call a week, with a demo. Thirty to forty-five minutes, same day and same time every week. I show you what got built, running. We go over what we learned and decide what goes into the following week. You leave with a short set of notes, not a slide deck. - A demo of what was built, not slides - Decisions for the coming week - Three lines of notes when we hang up ### Every Friday, something you can open. A build on your phone through TestFlight or Google Play, or a staging URL for the web. With it, a progress note in plain language: what was done, what was tested, what comes next. Nothing runs six weeks in the wrong direction. - A usable build or URL, not screenshots - A progress note you can forward to your partner - Whatever breaks gets said the same day ### A schedule that gets updated, not filed away. The milestones and their dates live in a shared document from day one. Every week I mark what was completed and, if something moved, I write down why. You always know where we are and what is left, without having to ask. - Dated milestones, visible to your whole team - Changes explained, never hidden - A “today” marker that is always where it should be ## A typical week, Monday to Friday. - MON, Priorities: I send you the three things for the week. You confirm, or swap one out. - TUE, Build: Code, open pull requests you can read, and quick questions on the channel. - WED, Build: The work continues. If something blocks it, you know that same day. - THU, Meeting: Demo, decisions and short notes. We adjust the schedule if we need to. - FRI, Delivery: A build or URL in your hands, a progress note, and what goes into next week. ## The first ten days, from your message to the first delivery. 1. Day 0, You write to me: WhatsApp, email or LinkedIn, with whatever you have: an idea, a Figma file, or an app that already exists. 2. Day 1, I reply with three questions: The ones needed to understand what you have today and what you want to achieve. 3. Day 3, A 30-minute call: We define the core use case, what goes into the first version and what can wait. 4. Day 5, A written proposal: Scope, milestones with dates, and what I need from your side. If something does not fit, we adjust it before starting. 5. Day 10, First week underway: Channel open, schedule shared and the first meeting booked. By Friday you already have something to open. ## Yours from day one, and what I need from you. ### What is yours - The repository, in your GitHub account - App Store, Google Play, domain and hosting accounts, in your name - The decisions document and the schedule - One progress note a week, ready to forward - Enough documentation for another developer to continue ### What I need from you - One person who can make a decision within 48 hours - Access and accounts from the start - One hour a week for the meeting and to try the delivery - Honest answers when something does not convince you ## Contact Two or three lines are enough: what product you have or want, who it is for, and what worries you. I reply the same day with the questions that are missing.