fix: remove stale seven-day sales promises - #16
Merged
Conversation
intended-outcome: active managed-service sales and operator copy matches fixed-scope Day 0 and 14-day tracking truth without a delivery guarantee. verify: npm run check, npm test, npm run ci, git diff --check passed; sgscan has only pre-existing warnings. Co-Authored-By: Claude <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
📝 WalkthroughWalkthroughThe offer and sales materials now use The Website Correction as a human-reviewed, fixed-scope engagement. Delivery language now specifies Day 0 initiation and 14-day implementation tracking. Contract tests reject stale seven-day delivery claims. ChangesOffer messaging update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/draft-sales-call-prep.mjs`:
- Line 153: Update the generated sales question in the draft content to use the
singular phrase “one implementation-ready page fix” instead of
“implementation-ready fixes,” preserving the one-page engagement scope aligned
with the canonical sales wording.
In `@scripts/test-sales-intake-contract.mjs`:
- Around line 115-137: Expand staleSevenDayPromise to reject duration-first
phrases such as “7-day fix” and “7-day delivery,” plus verb-based promises such
as “deliver in 7 days” and “complete within seven days.” Add representative
versions of each newly supported wording to the stale-pattern validation loop
while preserving the existing active-surface and historical benchmark checks.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 91c46e10-4870-4833-a1c6-dde1ef473f07
📒 Files selected for processing (10)
growth-brain/offer.mdgrowth-brain/prospecting/warm-network-scripts.mdgrowth-brain/sales/follow-up-sequences.mdgrowth-brain/sales/proposal-template.mdgrowth-brain/sales/sales-call-script.mdscripts/create-prospect-audit.mjsscripts/draft-sales-call-prep.mjsscripts/prepare-prospect-call-booked.mjsscripts/prepare-prospect-close-package.mjsscripts/test-sales-intake-contract.mjs
| 3. Who approves page, copy, or site structure changes? | ||
| 4. What context can you share: analytics, reviews, competitors, customer objections, and implementation access? | ||
| 5. If the sprint gives you implementation-ready fixes in 7 days, is this worth doing now? | ||
| 5. If the sprint gives you implementation-ready fixes plus 14-day implementation tracking, is this worth doing now? |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Use singular wording for the fixed one-page scope.
The canonical scope limits the engagement to one highest-leverage page. This generated question says implementation-ready fixes, which can imply multiple fixes or pages. Change it to one implementation-ready page fix to preserve the same sales contract used by Line 17 of growth-brain/sales/sales-call-script.md.
Proposed wording
-5. If the sprint gives you implementation-ready fixes plus 14-day implementation tracking, is this worth doing now?
+5. If the sprint gives you one implementation-ready page fix plus 14-day implementation tracking, is this worth doing now?📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 5. If the sprint gives you implementation-ready fixes plus 14-day implementation tracking, is this worth doing now? | |
| 5. If the sprint gives you one implementation-ready page fix plus 14-day implementation tracking, is this worth doing now? |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@scripts/draft-sales-call-prep.mjs` at line 153, Update the generated sales
question in the draft content to use the singular phrase “one
implementation-ready page fix” instead of “implementation-ready fixes,”
preserving the one-page engagement scope aligned with the canonical sales
wording.
Comment on lines
+115
to
+137
| const staleSevenDayPromise = /\b(?:seven[- ]day|7[- ]day) sprint\b|\b(?:fix(?:es)? in (?:7|seven) days|(?:7|seven) working days)\b|\bby the end of (?:7|seven) days\b/i; | ||
| const activeOfferSurfaces = [ | ||
| "growth-brain/prospecting/warm-network-scripts.md", | ||
| "growth-brain/sales/sales-call-script.md", | ||
| "growth-brain/sales/follow-up-sequences.md", | ||
| "growth-brain/offer.md", | ||
| "growth-brain/sales/proposal-template.md", | ||
| "scripts/create-prospect-audit.mjs", | ||
| "scripts/draft-sales-call-prep.mjs", | ||
| "scripts/prepare-prospect-call-booked.mjs", | ||
| "scripts/prepare-prospect-close-package.mjs" | ||
| ]; | ||
| for (const surface of activeOfferSurfaces) { | ||
| dnm(readFileSync(join(repoRoot, surface), "utf8"), staleSevenDayPromise, `${surface} still promises a seven-day delivery`); | ||
| } | ||
| dnm(callPrepOutput, staleSevenDayPromise, "sales-call-prep.md still promises a seven-day delivery"); | ||
| // Historical comparison context is deliberately outside this scan: the | ||
| // benchmark matrix keeps its labelled 7-day comparison row, and the check | ||
| // must not flag it. | ||
| mat(readFileSync(join(repoRoot, "docs/strategy/market-parity-benchmark-2026.md"), "utf8"), /\| Speed \| 2-6 week audit\/report \| 7-day sprint with implementation-ready assets \|/); | ||
| // Guard against pattern drift: each removed variant must still be caught. | ||
| for (const stale of ["seven-day sprint", "7-day sprint", "fix in 7 days", "7 working days from Day 0", "by the end of 7 days", "seven working days"]) { | ||
| mat(stale, staleSevenDayPromise); |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Expand the stale-promise matcher.
The regex does not reject 7-day fix, 7-day delivery, deliver in 7 days, or complete within seven days. An active surface can therefore reintroduce a seven-day delivery promise and still pass this regression test. Extend the matcher and the variant table to cover duration-first and verb-based wording.
Proposed matcher coverage
-const staleSevenDayPromise = /\b(?:seven[- ]day|7[- ]day) sprint\b|\b(?:fix(?:es)? in (?:7|seven) days|(?:7|seven) working days)\b|\bby the end of (?:7|seven) days\b/i;
+const staleSevenDayPromise = /\b(?:seven[- ]day|7[- ]day)\b|\b(?:fix(?:es)?|deliver(?:s|y|ed)?|complete(?:s|d)?|finish(?:es|ed)?)\s+(?:in|within|by)\s+(?:7|seven)\s+(?:working\s+)?days?\b|\bby the end of (?:7|seven)\s+(?:working\s+)?days?\b/i;
...
-for (const stale of ["seven-day sprint", "7-day sprint", "fix in 7 days", "7 working days from Day 0", "by the end of 7 days", "seven working days"]) {
+for (const stale of ["seven-day sprint", "7-day sprint", "7-day fix", "7-day delivery", "fix in 7 days", "deliver in 7 days", "complete within seven days", "7 working days from Day 0", "by the end of 7 days", "seven working days"]) {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@scripts/test-sales-intake-contract.mjs` around lines 115 - 137, Expand
staleSevenDayPromise to reject duration-first phrases such as “7-day fix” and
“7-day delivery,” plus verb-based promises such as “deliver in 7 days” and
“complete within seven days.” Add representative versions of each newly
supported wording to the stale-pattern validation loop while preserving the
existing active-surface and historical benchmark checks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
intended-outcome: active managed-service sales and operator copy matches fixed-scope Day 0 and 14-day tracking truth without a delivery guarantee.
verify: npm run check, npm test, npm run ci, and git diff --check passed with 126 checks; sgscan has only pre-existing warnings. Grok review: ship, best version of this scoped fix.
Co-Authored-By: Claude noreply@anthropic.com
Summary by CodeRabbit
Offer Updates
Sales & Prospecting
Tests