October 7, 2026
Riverbend website launch and Spanish pages
The team chose a five-page Spanish scope and moved launch to December 4, conditional on timely client inputs.
- $3,900 covers Spanish for five key pages; the full site was declined.
- Patrick owes Appointly production credentials by Friday.
- Megan owes five service-page texts by next Wednesday.
- The benefits campaign is planned for December 7, shortly after launch.
Demo meeting, people are fictional
🟡 The launch moves to December 4, conditional on Appointly’s production credentials and all five outstanding service-page texts arriving on time. The client owes both inputs; the only added fee is $3,900 for Spanish on five pages.
Easy to miss
- The benefits campaign is planned for December 7, three days after launch — the site has little time to be ready before the campaign starts; the client’s planned campaign date is already set.
Will the date hold
- The arithmetic: launch moves by two weeks; named delays are about eight working days, plus three to four days of Spanish build and QA, plus the translator’s usual week → these durations leave little apparent slack, though they mix working and unspecified days.
- Condition for the date: the launch holds only if Patrick delivers the production Appointly credentials by Friday and Megan delivers all five texts by next Wednesday; put both conditions in the change order.
- Capacity risk: Megan’s seven texts took about five weeks, while the remaining five are promised in one week. If they slip again, the team’s internal fallback is a copywriter at cost; trigger is missing the Wednesday deadline.
Internal — not for the client
- The team doubts the five texts will arrive on time: Megan is handling clinic marketing, hiring two hygienists, and the open house, alongside the stated five-week turnaround for the prior seven texts.
- If the texts miss Wednesday, offer Joanne, a dental-experienced copywriter, at cost with no margin; Megan would review and approve rather than draft from scratch. Do not raise it before the deadline.
- The team is willing to absorb a few hundred dollars for copywriting to protect the launch and account. It is already absorbing some time chasing the booking vendor.
Needed from the client
| What | Who on client side | By when; blocks |
|---|---|---|
| Provide production Appointly client ID and secret | Patrick | Friday; booking integration and launch |
| Deliver five service-page texts, with emergency care first | Megan | Next Wednesday; service pages and Spanish emergency page |
| Prompt Dr. Ahmed to review pediatric and periodontal content | Patrick | —; two service-page texts |
| Confirm whether Westgate has Spanish-speaking staff | Megan | —; clinic-page language badge |
| Sign Spanish change order | Patrick | —; translator and Spanish work |
Decisions and their cost
| Decision | What changes | Money or time impact |
|---|---|---|
| ✅ Translate five key pages, not the full site | Homepage, new patient, emergency care, insurance and payment, booking and contact | $3,900 total; translator, Rosa review if wanted, build and QA included; mostly fits within QA |
| ✅ Use proper Spanish URLs, language switcher and Google tags | Spanish pages can be expanded later without rebuilding | Included in the $3,900 |
| ✅ Use Appointly’s Spanish mode for booking and confirmations | Confirmation texts and emails follow the language of the booking page | Included; test especially carefully |
| ✅ Add “hablamos español” badges to confirmed clinic pages | Eastside and Riverbend; Westgate pending confirmation | No charge |
| ✅ Move launch to December 4 | One clean launch with Spanish pages and QA | Two weeks later; no fee for the date change |
| ❌ Full Spanish site | All pages, forms, booking flow and emails | $8,400 and about three weeks added; would put launch at mid-December or later |
| ❌ Machine-translation plugin | Would not provide indexed Spanish pages; clinical terms could be misleading | Technically an afternoon, but rejected for medical accuracy and search reasons |
| ❌ Launch Spanish pages after the main launch | Would split delivery and require another QA cycle and deploy | Costs more, and does not solve the existing content and booking risks |
| ❌ Add clinic pages to the initial Spanish scope | Clinic pages are mainly addresses, hours, maps and photos; priority is patient decision-making pages | More pages increase cost; not selected |
Our tasks
| Task | Owner | Due |
|---|---|---|
| Prepare the change order and updated timeline; send to Patrick and Megan | Kwame | Friday |
| Build a staging link with booking stub and “test booking” banner | Technical lead | October 16 |
| Send two proposed photography dates, ideally Saturdays | Laura | Friday |
| Send the redirects list, including the roughly 20 traffic-driving old blog posts | Kwame | — |
| Configure Spanish booking and confirmations; test the flow thoroughly | Technical lead | — |
| Wait for signed change order and translator’s first draft before asking Rosa to review | Laura | — |
Given away free
- The date change carries no fee.
- “Hablamos español” badges on confirmed clinics are included at no charge.
Suggested next move
- Make the input deadlines explicit in the change order — built from the agreed conditional December 4 date and the team’s concern that content is the real risk; include the agreed client inputs and the consequence for the schedule if they slip.
Critical path
Get notes like this from your own calls.
Add MeetWave to Chrome — no bot joins your meetings. Your first 30 days of Pro are on us. No card.
No install yet? Record your next call right here — no bot joins.