We would rather build than meet
Meetings are a cost, and you are the one paying it twice. Here is the small set we think earns its place, what each one is for, and how we keep everything else off your calendar.
Async by default, on purpose
Most of what happens in a status meeting is information that could have been written down and read in two minutes. We write it down instead.
What we keep live is the part that genuinely needs a conversation: decisions with trade-offs, work you need to see moving, and the occasional disagreement that is faster to resolve out loud.
If a call on our schedule stops being useful, tell us and we will drop it. Nobody has ever regretted having one fewer standing meeting.
The meetings that actually exist
Four of them, and only one is weekly. Everything here can be adjusted to fit how your organization already runs.
Kickoff, once
Longer than the rest and worth it. We agree on goals, constraints, who decides what, how we will reach each other, and what access we need. Most of the confusion later in a project traces back to something skipped here.
A short standing check-in
Weekly during an active build, every two weeks once things are steady. It exists to unblock, not to report. If there is nothing blocked, we cancel it rather than fill it.
A demo at the end of each cycle
You see working software rather than a progress percentage, and you shape what comes next. On quieter engagements this is a written summary with screenshots instead of a call.
A strategy call
Quarterly on the entry retainer tier, monthly a step up, and every two weeks at the top. This is the one where we stop talking about tickets and talk about the next six months.
The unscheduled one
Something broke, a decision needs making today, or a reporter called. We will get on a call the same day when it warrants one, and we do not charge you extra for it.
What this costs you in hours
Rough figures from how our engagements actually run. Yours will vary with how much is in flight, and we would rather set the expectation than let you find out in month two.
The standing check-in
Short by design, and cancelled when there is nothing to unblock. One person from your side is usually enough.
The strategy call
The entry tier includes a quarterly strategy call. Higher tiers move that to monthly and then to every two weeks, with a dedicated channel for urgent items at the top.
Total time on your calendar
An active build costs more than that while it runs. A settled retainer often costs less. Either way, you are not spending your week in status meetings.
Questions about how we work
- How many meetings should we expect in a month?
-
On a steady engagement, usually one short check-in every week or two plus a strategy call whose cadence matches your tier, which works out to roughly one to two hours a month in total.
An active build costs more than that while it runs, because you are seeing work and shaping what comes next every two weeks. If a standing call stops being useful, we drop it.
- Can we work mostly over email and chat instead of calls?
-
Yes, and plenty of our clients do. We work in the channel you already use, keep a shared backlog you can see, and send a written summary at the end of each cycle covering what shipped, what is next, and what is blocked.
The one thing we ask for live is kickoff. Decisions about who approves what and how we reach each other are much faster in conversation, and skipping it causes problems later.
- Who from our side needs to be in these meetings?
-
Fewer people than you think. One person who can approve priorities and unblock us needs to be at the check-ins. Kickoff benefits from whoever holds the goals and whoever knows how the current setup works, which is often two different people.
Everyone else can read the written summary. Meetings where half the room is listening politely are expensive for you, not for us.
- What does a two-week sprint with you include?
-
A sprint starts with a shared backlog and an agreed set of priorities. Most of it is roadmap work: new pages, features, and fixes you asked for. We also hold back capacity for the things that show up mid-sprint, like an urgent press release or a same-day fix. At the end of every sprint you see what shipped, what is next, and what is blocked.
- How fast do you respond to emergencies?
-
Response SLAs are tier-dependent and written into your contract. The Steady tier is within two business days for non-urgent work and within twenty-four hours for site-down emergencies. Active and In motion tiers tighten that further.
- Who will I be talking to?
-
The people who would actually do the work. You will not be handed to a salesperson and then reintroduced to a delivery team later.
Want to know what this would look like on your calendar?
Tell us how your team already communicates and we will fit around it rather than asking you to adopt our habits.
The consultation itself is about thirty minutes, which is a fair sample of how we run a call.