The Person Who Scopes the Project Never Operates the Integration#26
Draft
superterran wants to merge 1 commit intomainfrom
Draft
The Person Who Scopes the Project Never Operates the Integration#26superterran wants to merge 1 commit intomainfrom
superterran wants to merge 1 commit intomainfrom
Conversation
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
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.
📝 Blog Draft — The Constellation
Hook: The most expensive gap in mid-market commerce isn't a missing feature; it's the fact that the person who writes the integration estimate has never been paged at 2 AM when the order sync breaks.
Angle: Integration scoping in commerce projects is almost always done by someone who will never operate the integration in production. This creates a structural incentive to undercount edge cases, error handling, retry logic, monitoring, and runbook documentation. The result is integrations that work on demo day and degrade silently in production. The fix is not better estimation templates. It is putting an operator's voice in the scoping room before the SOW is signed.
Source material: bai/transcripts/plaud-2026-03-23-03-23-meeting-sales-to-delivery-handoff-process-sow-accountability-and-ai-tools.md (handoff gaps, SOW accountability, missing business context in delivery); bai/transcripts/plaud-2026-04-02-04-02-interview-ali-hashmi-e-commerce-architecture-integrations-and-performance-strategy.md (integration source of truth, unclear data ownership); bai/skills/external-context-index/state.md (Aramark Elevate integration bottlenecks, estimate compression); Personal/Career/Public Voice - Positioning and Editorial POV.md (Constellation pillar: integration architecture is 80% of the outcome)
Draft is in
dotcom/content/blog/2026-05-05-person-who-scopes-never-operates-integration.md. Edit directly on this branch or merge as-is.To publish: merge this PR. The
blog-publishworkflow will auto-generate a LinkedIn post and cross-post it.To discard: close without merging.