How we work / Sample weekly update
What the weekly update looks like
Every active project gets one of these in writing, every week, without being asked. It's how a project stays inspectable from another continent — you always know what moved, what's stuck, and what we need from you.
Sample format — this is the document format you receive on a real engagement. Everything below is illustrative: the business, numbers, and findings are examples, not client data.
Format: Email, ~1 screen
Cadence: Every Friday, your timezone
Project: Store ↔ accounting integration (illustrative)
Subject: Week 3 of 5 — order sync live on staging
Done this week
- Order and refund events now flow to the accounting system on staging — including partial payments
- Customer matching live: 92 of the 96 test customers matched automatically; 4 queued for your confirmation (10-minute task, link below)
- Duplicate-event protection tested by replaying last month's order export twice — zero duplicate invoices
In progress
- Tax mapping table for EU customers — on track, no surprises
- The status dashboard your team will use to answer 'did it sync?'
Blocked / decisions needed from you
- Those 4 ambiguous customer matches need a yes/no from whoever knows the accounts
- Confirm: should credit-terms orders create the invoice at order time or at fulfillment?
Next week
- Dashboard finished and shared for your review
- End-to-end run on a full week of real staging data
Where to look
Staging: [link] · Review queue: [link] · Scope status: on budget, week 3 of 5, no change requests open.
Want documents like this about your systems?
Describe the problem in plain language — broken, slow, manual, or missing. We'll tell you honestly whether and how we can help.
- 01We reply within one business day
- 02A short call to understand the problem
- 03A written scope and fixed quote — no obligation