Skip to content

Landing page: Teams is booked as a call, not bought - #543

Merged
chaitanyagiri merged 1 commit into
mainfrom
teams/booking-landing
Sep 17, 2026
Merged

chaitanyagiri merged 1 commit into
mainfrom
teams/booking-landing

Conversation

@chaitanyagiri

Copy link
Copy Markdown
Owner

One file, docs/index.html. Teams stops selling itself from the public page and Pro is not touched.

What changed

Every Teams price is off the page. $39 a seat a month, $399 a seat a year and the $195 a month for 5 seats running total are all gone, and nothing replaced them with a smaller number or a range. The size slider, the 14 day trial chip on the Teams tier, the card at checkout sentence and the JavaScript that drove the slider went with them. The tier now reads By call, thirty minutes, set up with us.

All four Teams calls to action point at one place, https://cal.com/chaitanya-giri-dk45ov/30min:

where was now
hero link under the download button harnessmd.com/console, text "Munder Difflin for Teams" the calendar, text "Talk to us about Teams"
Teams feature card cal.com/chaitanya-giri-w3wrwi/munder-difflin-teams-demo, an older and different calendar the calendar
pricing tier button harnessmd.com/console, text "Start a team" the calendar
closing button harnessmd.com/console, text "Start a team" the calendar

The feature card carried a second, older calendar link. It is replaced, not joined, so exactly one booking destination exists on the site now.

Two answers rewritten in the FAQ. "Will Teams charge me during the trial?" became "How do I get Teams?", and the cost answer prices Teams with the team on the call instead of quoting per seat figures. The Free and Pro figures in that answer are unchanged.

The download line said paid plans start with a 14 day trial. Only Pro does now, so it names Pro.

Why the calendar and not /teams/talk

An intent form at /teams/talk would also catch someone who reads the page and does not book, and that is still the plan. It is not built yet and it needs your own answers first, so pointing a live public page at a route that does not exist would be a dead end. The four links go to the calendar today and move to the form in one edit when it ships. The comment above the pricing section in the file says exactly this so nobody has to rediscover it.

What was deliberately not touched

Pro keeps its styling, its copy and its three figures ($200 struck, $150 a year, $20 a month). Free is unchanged. The release version stays 0.4.6 and npm run check:links passes: ✓ release links consistent at v0.4.6.

How to check it

Rendered locally and read back out of the live DOM. Every dollar figure remaining on the page is $0, $20, $150, $200, all of them Free or Pro. The four Teams links resolve to the calendar. document.getElementById('seats') and getElementById('teamTotal') are both gone, so the slider script has nothing orphaned to drive.

Branch is rebased on main at 34f2749, so the Google Ads tag from #540 is already underneath it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PogxmT9ULRQSYbfs1oigLx

The Teams tier no longer sells itself. The per seat month price, the per seat year price, the size slider with its running total, the trial chip and the card at checkout sentence are all gone, and nothing replaced them with a smaller number or a range. The tier says instead that Teams is arranged with us on a call. The FAQ says the same: the answer about being charged during a trial is now an answer about how you get Teams at all, and the cost answer prices Teams with the team on the call. The free and Pro figures are untouched, and so is the Pro styling, the Pro copy and the release version.

All four Teams calls to action now point at the same place, https://cal.com/chaitanya-giri-dk45ov/30min: the hero link that used to read Munder Difflin for Teams, the Teams feature card, the pricing tier button and the closing button. The feature card used to carry a second, different calendar link, which is now gone, so exactly one booking destination exists on the site.

The calendar is the destination on purpose and for now. An intent form at /teams/talk would also catch someone who reads the page and does not book, but it is not built yet and it needs the founder's own answers first. Pointing a live public page at a route that does not exist would be a dead end, so the four links go to the calendar today and move to the form in one edit when it ships. The comment above the pricing section says so.

The download line said paid plans start with a 14 day trial. Only Pro does now, so it names Pro.

The seat slider script and the CSS for the slider and its total went with the markup it drove. What a company evaluating Teams still needs is kept: what Teams does, the sealed per device answer, the admin console, and that each person runs under their own keys.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PogxmT9ULRQSYbfs1oigLx
@github-actions

Copy link
Copy Markdown
Contributor

🚫 This PR is missing its before/after evidence

Every pull request here has to show its work. Screenshots or a short screen recording, before the change and after it.

  • Before — no image or video under that heading
  • After — no image or video under that heading

How to fix it: edit the description, keep the ### Before and ### After headings from the template, and drag an image or video under each. GitHub uploads it inline. This check re-runs the moment you save.

A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine.

Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the no-visual-change label. Please don't ask unless it truly has no observable effect.

📖 CONTRIBUTING.md → Evidence is mandatory

@chaitanyagiri chaitanyagiri reopened this Sep 17, 2026
@chaitanyagiri
chaitanyagiri merged commit 1b19614 into main Sep 17, 2026
6 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant