--- title: "How an engagement runs, week by week" description: "An engagement runs on a weekly rhythm, from the first week through the handoff. You see a working demo every week and end with your team running it." canonical: "https://www.pollyester.com/process" --- [Pollyester](https://www.pollyester.com/index.md) › How an engagement runs, week by week Process # The first week, every week after, and the last one. This page walks the rhythm of an engagement: how it starts, what a normal week feels like, and how it ends with your team running the thing we built together. For the shapes an engagement can take, see [Engagement](https://www.pollyester.com/engagement.md). [Start a conversation →](https://www.pollyester.com/contact.md) ![A silk filament looping in a steady returning cadence](https://www.pollyester.com/process/hero.dark.webp) Week one we're already building, and you can already see it. Every week a demo of the real thing running, not a deck about it. The handoff planned from the start, your team running it before we step back. The loop ## You'll watch the work take shape, week after week. From the first week the work lives in your accounts, under your name, and every week we sit down and show you the real thing running. Not a report about progress, the actual software doing its job. That rhythm is the whole point: you see where the work is going early, so you can change course while the change is still cheap. The rhythm ## What actually happens once we start. The thinking behind the work is our operating model, the seven waves, and it lives on [Method](https://www.pollyester.com/method.md). This page is the calendar, where that thinking shows up week to week. 01 + Week one ### We start building, not orienting The first week isn't a parade of kickoff meetings. We get access to your systems, open one shared channel, and put the working rhythm on the calendar, and then we start building. The plan from scoping becomes the first build targets, and we write down the honest starting point, the Truth work in our method, so everyone is measuring from the same line. Before that first week is out you've seen real work land, and you know what the first demo will show. 02 + Every week ### The demo is the heartbeat Most of the week we're heads down building, with your team in the thread and questions answered while they're still warm. Then we show you the demo: working software, never a deck. We look at it together, decide what changes, and your feedback turns into changed work or a written decision while the conversation is still fresh. Every week you have something real to show your own team. 03 + Mid-engagement ### When the scope moves, you hear it first Something always shifts partway through. A system turns out to be in worse shape than anyone knew, or a bigger win shows up right next to the one we scoped. When that happens you hear it from us first, in writing, with what it means for timeline and budget laid out plainly. Then you decide, because it's your call to make. No surprise invoice at the end of the month. 04 + Ship week ### It goes live and gets measured The work goes live and gets read against the starting point we wrote down together at the beginning. Where a model is making decisions, we hold back a slice of customers who don't get it, so the lift you see is real and not a story we're telling ourselves. You see the number move, or you hear the truth about why it hasn't yet. 05 + The last stretch ### The handoff is planned, not sprung Own, the last wave in our method, is on the calendar from the start. We write things down as we build, so by the end your team has the docs and the plain instructions for running everything, and there's a stretch where they run the loop while we're still in the room to catch what wobbles. After that we stay only as long as we're genuinely useful. Your team is running it before we're gone. You see it happen ## You're never guessing where the work is. Three things you can count on from the first week. 01 ### A working demo, every week Not a status update. We show you the actual thing running, and we talk about what it should do next. 02 ### Yours from the first week Everything we build lives in your accounts, in your name, from the start. Nothing is locked to us, and your team can look at any of it, run any of it, and build alongside us whenever they want. 03 ### One shared channel You're in the same conversation we are. Questions get answered the day you ask them, not saved up for a status call. How we work ## Five things we hold to, on every engagement. Not a list of tools or credentials, just the way we actually work. 01 ### Listen before we build We don't show up with a plan and start executing it. The first stretch is spent reading your systems and sitting with your team, because the plan is only as good as what it's built on. 02 ### Demo in working software Every week we show you something running. A deck is not a deliverable here, and it never has been. 03 ### Partners on the keyboard The people who pitch you are the people who build it. A partner is in the daily conversation and in the work itself, because that's where the real calls get made. 04 ### The truth on the table We tell you what we actually find, including 'you don't need that yet,' even when saying it makes the engagement smaller. 05 ### Build for the handoff From the first day we work like people who are leaving. We write things down as we go, we keep your team close to the work, and we treat a clean handoff as the point of the whole thing, not something we lose by. Questions ## The things people ask before we start. How much of our time do you need? + Less than you'd fear. A few hours a week from the person who owns the outcome, a bit more from the people closest to the systems. We're careful with everyone's calendar, because we've sat on your side of it. What if the scope changes partway? + It usually does, and that's fine. When it happens we lay out what it means for timeline and budget, put the change in writing, and adjust once you've agreed. You're never finding out from an invoice. Do we see the work as it happens? + From the start. Everything lives in your accounts, in your name, so your team can look at it, run it, and work alongside us whenever they like. How do feedback and revisions work? + Mostly through the weekly demo, plus short walkthroughs as pieces land. You tell us what's off, and it becomes either changed work or a written decision while the conversation is still warm. Can you build it for us, or with our team? + Either, honestly. Some brands want it handed over finished, some want us shoulder to shoulder with their own people the whole way through. We shape the engagement around how you like to work. What happens after handoff? + We don't wave and vanish. There's a stabilization stretch built in, with your team running things while we're still close enough to help. After that we're around in whatever shape is useful to you, and no subscription is required. Where the rhythm ends ## When we're done, the loop keeps running. That's the test we hold ourselves to. At the end you're not holding a report about the work, you're holding the work itself: the software, the docs, the know-how, and a team of your own people who can run it without calling us. ### Let's talk. Tell us where you're trying to grow. We'll tell you the truth about how to get there. [Start a conversation →](https://www.pollyester.com/contact.md) --- ## Pollyester — site navigation Primary: [Services](https://www.pollyester.com/services.md) · [Work](https://www.pollyester.com/work.md) · [Partners](https://www.pollyester.com/partners.md) · [About](https://www.pollyester.com/about.md) · [Ideas](https://www.pollyester.com/blog.md) Company: [About](https://www.pollyester.com/about.md) · [Careers](https://www.pollyester.com/careers.md) · [Contact](https://www.pollyester.com/contact.md) · [How a project runs](https://www.pollyester.com/process.md) · [Engagement](https://www.pollyester.com/engagement.md) Services: [Get found](https://www.pollyester.com/services/get-found.md) · [Get chosen](https://www.pollyester.com/services/get-chosen.md) · [Grow the customer](https://www.pollyester.com/services/grow-the-customer.md) · [Earn advocacy](https://www.pollyester.com/services/earn-advocacy.md) · [Pick, pack & ship](https://www.pollyester.com/services/pick-pack-ship.md) · [Order orchestration](https://www.pollyester.com/services/order-orchestration.md) · [Cost optimization](https://www.pollyester.com/services/cost-optimization.md) · [Build the agent-ready core](https://www.pollyester.com/services/build-the-agent-ready-core.md) · [Brand & identity](https://www.pollyester.com/services/brand-identity.md) · [Creative & art direction](https://www.pollyester.com/services/creative-art-direction.md) · [Content & campaigns](https://www.pollyester.com/services/content-campaigns.md) · [Video & media](https://www.pollyester.com/services/video-media.md) · [Storefront & product](https://www.pollyester.com/services/storefront-product.md) · [Experiential & activations](https://www.pollyester.com/services/experiential-activations.md) · [Events & retail](https://www.pollyester.com/services/events-retail.md) · [Design & build](https://www.pollyester.com/services/design-build.md) Legal: [Privacy](https://www.pollyester.com/privacy.md) · [Terms](https://www.pollyester.com/terms.md) Full index: [llms.txt](https://www.pollyester.com/llms.txt) — the markdown map of the site.