Cross-functional · launching December 31, 2026

Practitioner Website Consolidation

Three practitioner platforms becoming one, with the specification layer written between Marketing and IT.

Three practitioner platforms are being consolidated into one. The project spans IT, Accounting, and Marketing, and it needed a precise written account of what the consolidated platform must do, in terms both Marketing and IT could build from.

I was selected as the cross-functional bridge between IT, Accounting, and Marketing. I author the specification layer: a workflows document, a decisions sheet, and a clickable HTML prototype.

Along the way I surfaced a tax compliance requirement missing from all project documentation, W-9/TIN and verified banking before proceeds accrue, and drove it into the ERP design.

Practitioner Website Consolidation: specification flowThree practitioner platforms feed a specification layer made of a workflows document, a decisions sheet, and a clickable HTML prototype. A tax compliance requirement, W-9/TIN and verified banking before proceeds accrue, acts as the guardrail. Marketing and IT work from one specification, and the output is one platform, launching December 31, 2026, with the requirement in the ERP design.SourceThree practitioner platformsProcessingSpecification layer: workflowsdocument, decisions sheet, clickableHTML prototypeGuardrailTax compliance requirement: W-9/TINand verified banking before proceedsaccrueHuman reviewMarketing and IT work from onespecificationOutputOne platform, launching December 31,2026, with the requirement in the ERPdesign
Practitioner platforms
3 → 1
Launch
Dec 31, 2026
Tax compliance requirement surfaced that no project document had
1

Turn the tax compliance requirement into test cases, so the launch is checked against it, not only designed for it.

  • Specification writing
  • Workflows document
  • Decisions sheet
  • HTML prototype
  • ERP design