{ "rsa": [ { "id": "claims", "name": "Claims operations", "audience": "Claims leaders and payer operations teams evaluating help with repeatable administrative claims work.", "intent": "Commercial investigation and solution selection", "promise": "Reduce repetitive claims administration so the team can focus on exceptions that need attention.", "headlines": [ "Claims Work Piling Up?", "Automate Routine Claims Tasks", "Give Claims Teams Time Back", "Built For Payer Operations", "SymKey Claims Automation", "Less Repetitive Claims Work", "Keep Your Core System", "Put Business Rules To Work", "Focus People On Exceptions", "A Clearer Path Through Claims", "Explore The Claims Module", "See SymKey For Your Team", "Make Routine Work Repeatable", "See What Ran And When", "Plan Your Next Workflow" ], "descriptions": [ "Help your claims team spend less time on repeatable tasks. Explore SymKey for payers.", "Use your business rules to automate routine work in your existing claims system.", "Start with a defined claims workflow. See how SymKey handles tasks and logs actions.", "Bring your operations questions. Explore where the Claims module fits your team." ], "displayPaths": [ "claims", "automation" ], "finalURL": "https://hcim.com/symkey-claims-module/", "conversion": "A qualified inquiry requesting a discussion of a specific claims workflow.", "landingPageMessage": "Your claims specialists have more valuable work than repeating the same administrative steps. Explore which routine workflows SymKey can support in your existing environment.", "testingNote": "Compare the backlog/problem message with the capacity/benefit message while holding audience, destination, and offer steady. Review actual served combinations; an RSA can combine assets in different orders." }, { "id": "provider", "name": "Provider data operations", "audience": "Provider data, network operations, and payer administration leaders responsible for routine provider maintenance.", "intent": "Commercial investigation and solution selection", "promise": "Make repeatable provider administration more manageable without treating exceptions as routine.", "headlines": [ "Provider Updates Piling Up?", "Automate Provider Admin", "Less Repetitive Provider Work", "Help Your Provider Data Team", "SymKey Provider Module", "Make Routine Updates Easier", "Put Your Rules Into Action", "Support Provider Operations", "Work In Your Current System", "Give Specialists Time Back", "Start With One Workflow", "Track The Work That Runs", "A Clearer Update Process", "Explore Provider Automation", "See Where SymKey Fits" ], "descriptions": [ "Support provider operations with automation for repeatable administrative workflows.", "Apply your business rules to routine work. Give your team more room for exceptions.", "Explore the SymKey Provider module for work in your existing core system.", "Choose one provider workflow to review. Understand fit, rules, and action logging." ], "displayPaths": [ "provider", "automation" ], "finalURL": "https://hcim.com/symkey-provider-module/", "conversion": "A qualified inquiry identifying a provider administration workflow and its owner.", "landingPageMessage": "When routine provider work keeps returning to the queue, more effort alone is not a process improvement. Explore how defined business rules can support repeatable administration.", "testingNote": "Test the recurring-update problem against the team-capacity benefit. Separate provider administration queries from consumer searches for a healthcare provider." }, { "id": "authorizations", "name": "Authorization administration", "audience": "Authorization operations and payer leaders evaluating repetitive administrative workflow support.", "intent": "Commercial investigation and solution selection", "promise": "Support repeatable authorization administration while preserving the appropriate human review.", "headlines": [ "Authorization Admin Adds Up", "Less Repetitive Admin Work", "Support Authorization Teams", "SymKey Authorizations", "Put Defined Rules To Work", "Help Teams Focus On Review", "Streamline Routine Steps", "Keep Human Review In Focus", "Work In Your Existing System", "Explore A Clearer Workflow", "Make Admin Work Repeatable", "Log Automated Actions", "Start With Workflow Fit", "See SymKey For Payers", "Review Your Routine Tasks" ], "descriptions": [ "Explore automation for routine authorization administration in payer operations.", "Support repeatable tasks with defined rules. Keep appropriate human review in place.", "See how SymKey can fit your existing system and log the administrative actions it runs.", "Map your workflow, rules, and exceptions. Find a practical place to start with SymKey." ], "displayPaths": [ "authorizations", "workflows" ], "finalURL": "https://hcim.com/symkey-authorizations-module/", "conversion": "A qualified discussion of administrative authorization workflow fit.", "landingPageMessage": "Free up attention for the work that needs it. Explore defined administrative tasks around authorizations, with clear boundaries for clinical judgment and exception handling.", "testingNote": "Keep administrative workflow language explicit. Exclude patient status, denial appeal, and treatment-approval searches when they do not reflect a payer buying a workflow solution." }, { "id": "eligibility", "name": "Eligibility administration", "audience": "Membership, enrollment, and eligibility operations leaders at payer organizations.", "intent": "Commercial investigation and solution selection", "promise": "Reduce repeated administrative effort in well-defined eligibility workflows.", "headlines": [ "Eligibility Work Adds Up", "Automate Routine Eligibility", "Help Your Eligibility Team", "SymKey Eligibility Module", "Less Repetitive Admin", "Support Membership Operations", "Put Business Rules Into Action", "Keep Your Current Core System", "Give Teams Room To Focus", "Start With A Defined Workflow", "Make Routine Work Repeatable", "See Automated Action Logs", "Explore Eligibility Workflows", "A Practical Automation Start", "See Where SymKey Can Help" ], "descriptions": [ "Explore SymKey for repeatable eligibility administration in your existing core system.", "Apply defined business rules to routine work and keep exceptions visible to your team.", "Help eligibility teams spend less time repeating administrative steps. Explore SymKey.", "Review the workflow, ownership, and logs before choosing what to automate next." ], "displayPaths": [ "eligibility", "automation" ], "finalURL": "https://hcim.com/symkey-eligibility-module/", "conversion": "A qualified inquiry from a payer team with an identifiable eligibility workflow.", "landingPageMessage": "Routine eligibility work should not consume all of your team's attention. Start with a clear workflow, defined rules, and a plan for the cases that need human review.", "testingNote": "Distinguish payer administration from consumer coverage checks and provider billing eligibility tools. Evaluate search terms before broadening reach." } ], "ads": [ { "id": "claims", "name": "Give claims teams time for exceptions", "intro": "Claims work piling up? SymKey helps automate repeatable administration so your team can focus on exceptions. Explore the Claims module.", "headline": "Give your claims team more time for the work that needs them", "cta": "Learn more", "onImageHeadline": "Give your claims team time for the exceptions.", "onImageSubhead": "Automation for repeatable claims administration.", "audience": "US payer claims and operations leaders: Director of Claims, Claims Operations Manager, VP Operations, and equivalent responsibilities at health plans and third-party administrators.", "destination": "https://hcim.com/symkey-claims-module/", "funnelStage": "Problem-aware to solution-aware", "benefit": "Connect repetitive administrative work to constrained claims-team capacity, then offer a specific module and workflow discussion.", "visualBrief": "Use the approved HCIM claims creative. Make the operational benefit and payer audience clear. Avoid patient information, invented product interfaces, and unverified performance numbers.", "test": "Compare a backlog/problem headline with a capacity/benefit headline in the same claims audience and destination. Evaluate qualified workflow inquiries as well as click cost." }, { "id": "provider", "name": "Make provider administration more manageable", "intro": "Provider updates keep coming. Explore SymKey for repeatable administration, using your business rules in your existing core system.", "headline": "Give provider operations a clearer way through routine work", "cta": "Learn more", "onImageHeadline": "Less repetitive provider work. More room to focus.", "onImageSubhead": "Explore the SymKey Provider module.", "audience": "US payer provider-data and network-operations leaders, supported by operations and enterprise-applications stakeholders responsible for provider administration.", "destination": "https://hcim.com/symkey-provider-module/", "funnelStage": "Problem-aware to product evaluation", "benefit": "Address recurring provider administration with a defined workflow, business rules, and a relevant product conversation.", "visualBrief": "Use the approved HCIM provider creative. Keep the provider-administration context explicit so the image is not mistaken for advertising clinical care. Use brand-approved blue, white, and gold.", "test": "Compare recurring-work and team-capacity messages within the same qualified provider-operations audience. Check inquiry roles and workflow needs before calling a message successful." }, { "id": "workflow", "name": "One workflow, a clear starting point", "intro": "Claims. Provider data. Authorizations. Eligibility. Start with one repeatable workflow and see where SymKey fits your existing core system.", "headline": "A practical place to start payer workflow automation", "cta": "Learn more", "onImageHeadline": "Start with one workflow. Make room for better work.", "onImageSubhead": "Claims · Provider · Authorizations · Eligibility", "audience": "US payer operations and IT leaders jointly evaluating workflow automation; use relevant company lists where available, with size and role criteria validated against HCIM's sales fit.", "destination": "https://hcim.com/symkey/", "funnelStage": "Solution-aware and evaluation", "benefit": "Reduce the perceived complexity of getting started by focusing on a bounded workflow with explicit rules and exceptions.", "visualBrief": "Create a clean HCIM-branded typographic composition with four labeled workflow areas and one clearly emphasized starting point. Avoid visual promises of automatic transformation or unsupported integration claims.", "test": "Test a workflow-focused headline against a capacity-focused headline. Keep the offer consistent: explore the module and discuss an actual operational workflow." } ], "personas": [ { "id": "economic-buyer", "name": "The operations executive", "roles": [ "Chief Operating Officer", "VP of Payer Operations", "Head of Operations" ], "organization": "Health plan, third-party administrator, or managed-care organization with repetitive administrative workload and an accountable process owner.", "jobToBeDone": "Create sustainable operational capacity while protecting service quality and managing change.", "trigger": "A growing queue, capacity pressure, recurring rework, or a strategic mandate to improve operations.", "objection": "Will this improve an important workflow, or create another tool for the team to manage?", "message": "Start with one material workflow, establish a baseline, and agree on the operating result and ownership before expanding.", "proofNeeded": [ "Workflow-specific demonstration", "Documented baseline and measurement plan", "Clear responsibilities and rollout boundaries" ], "cta": "Discuss a priority workflow with the operations and technical owners.", "qualification": "A defined operational problem, a relevant core environment, an internal owner, and willingness to validate fit." }, { "id": "claims-champion", "name": "The claims operations champion", "roles": [ "Director of Claims", "Claims Operations Manager", "Claims Process Improvement Lead" ], "organization": "Payer claims operations where repeatable administrative steps compete with exceptions for staff attention.", "jobToBeDone": "Keep routine work moving and preserve experienced staff time for complex cases.", "trigger": "The same types of work repeatedly return to the queue or require multiple handoffs.", "objection": "Our exceptions are complicated; a generic automation pitch does not reflect how the work gets done.", "message": "Separate repeatable tasks from exceptions. Evaluate a specific process using your actual business rules.", "proofNeeded": [ "A walk-through of the relevant claims tasks", "Explicit exception handling and escalation", "Visibility into actions taken" ], "cta": "Bring one claims workflow to a fit discussion.", "qualification": "The team can describe the workflow, its rules, volume, exceptions, and current owner." }, { "id": "technical-evaluator", "name": "The technical evaluator", "roles": [ "CIO", "IT Director", "Automation Lead", "Enterprise Applications Lead" ], "organization": "A payer organization evaluating how automation would operate within its existing systems and governance.", "jobToBeDone": "Understand environment compatibility, access, operational control, and ongoing support before approving a change.", "trigger": "Operations requests automation or a vendor comparison requires a technical review.", "objection": "How will this work in our environment, and who owns maintenance, access, and failure handling?", "message": "Make workflow fit, access, action visibility, change handling, and accountability explicit in the evaluation.", "proofNeeded": [ "Environment-specific technical discussion", "Security and access review appropriate to the organization", "Support and change-management responsibilities" ], "cta": "Arrange a joint operations and IT workflow review.", "qualification": "The core environment and technical constraints can be reviewed with an authorized stakeholder." }, { "id": "administration-owner", "name": "The administrative workflow owner", "roles": [ "Provider Data Director", "Membership Operations Manager", "Eligibility Operations Lead", "Authorization Operations Director" ], "organization": "Payer teams maintaining provider, eligibility, membership, or authorization administration workflows.", "jobToBeDone": "Reduce repeated administrative effort while keeping ownership and exceptions clear.", "trigger": "Recurring updates, inconsistent handoffs, a manual queue, or time spent checking the same work repeatedly.", "objection": "Our process varies by business rule, source, and exception. What happens when a case does not fit?", "message": "Document the common path, define the boundary, and identify the human handoff before automating repeatable steps.", "proofNeeded": [ "Relevant module demonstration", "Business-rule mapping", "A clear review and escalation process" ], "cta": "Explore the module that corresponds to the team's workflow.", "qualification": "A repeatable administrative process exists with an owner who can define routine work and exceptions." }, { "id": "finance-partner", "name": "The finance and improvement partner", "roles": [ "CFO", "Finance Director", "Operational Excellence Lead", "Transformation Lead" ], "organization": "Payer leadership evaluating the business case for a workflow improvement.", "jobToBeDone": "Separate plausible operating value from unsupported savings and build a decision-ready business case.", "trigger": "Budget planning, capacity requests, vendor evaluation, or expansion of a successful initial workflow.", "objection": "Time saved is not automatically cash saved. How will we know whether this is worth expanding?", "message": "Measure the actual operational change, the capacity it releases, the cost to operate, and what the organization can do with that capacity.", "proofNeeded": [ "Baseline with a defined measurement period", "Cost and ownership assumptions", "An agreed expansion decision" ], "cta": "Review the workflow measurement plan with operations.", "qualification": "The team can agree on costs, measurable outcomes, and a realistic evaluation period." } ], "keywords": { "status": "Research-led seed plan. Search volume, auction CPC, competitive density, and forecast reach have not been measured in a live keyword-planning account.", "geography": "US is the proposed first-market test; confirm HCIM's actual sales coverage before launch.", "demographicApproach": "Business role, organization type, workflow responsibility, and buying situation define the audience. Age, gender, ethnicity, and personal health are not used as proxies for a qualified buyer.", "matchApproach": "Start with tightly grouped exact and phrase keywords. Expand only after search-term quality, conversion tracking, and qualified inquiry feedback are reliable. The phrases below are seeds, not a finalized account import.", "groups": [ { "id": "claims", "name": "Claims automation for payers", "intent": "High commercial intent", "phrases": [ "claims automation software for payers", "health plan claims workflow automation", "payer claims administration automation", "claims operations automation", "automate repetitive claims tasks" ], "destination": "https://hcim.com/symkey-claims-module/", "watchout": "Separate payer administration from personal insurance claims and provider revenue-cycle software." }, { "id": "provider", "name": "Provider administration", "intent": "High commercial intent with ambiguity to inspect", "phrases": [ "provider data workflow automation", "payer provider administration automation", "provider maintenance automation", "health plan provider updates automation", "provider operations automation software" ], "destination": "https://hcim.com/symkey-provider-module/", "watchout": "Watch consumer provider searches, clinical services, and directories; do not exclude useful provider-data queries too broadly." }, { "id": "authorizations", "name": "Authorization administration", "intent": "Commercial intent; distinguish administrative and clinical needs", "phrases": [ "payer authorization workflow automation", "authorization administration automation", "health plan authorization operations software", "automate authorization administrative tasks", "authorization workflow tools for payers" ], "destination": "https://hcim.com/symkey-authorizations-module/", "watchout": "Exclude patient approval-status queries and unsupported clinical-decision needs rather than claiming medical decision automation." }, { "id": "eligibility", "name": "Eligibility administration", "intent": "Commercial intent with payer-fit qualification", "phrases": [ "payer eligibility workflow automation", "health plan eligibility administration", "eligibility maintenance automation", "membership operations automation", "automate eligibility administrative tasks" ], "destination": "https://hcim.com/symkey-eligibility-module/", "watchout": "Provider billing verification and consumer benefit eligibility can be different buying needs; inspect the actual query before excluding." }, { "id": "category", "name": "Payer workflow automation", "intent": "Category evaluation", "phrases": [ "payer workflow automation software", "health plan workflow automation", "automation vendor for health plans", "RPA for health insurance payers", "managed care administrative automation" ], "destination": "https://hcim.com/symkey/", "watchout": "Use only if the budget can support a separate category ad group without starving module-level learning." }, { "id": "brand", "name": "HCIM and SymKey", "intent": "Navigational and product evaluation", "phrases": [ "HCIM SymKey", "SymKey claims module", "SymKey provider module", "SymKey authorizations module", "SymKey eligibility module" ], "destination": "https://hcim.com/symkey/", "watchout": "Report brand separately from non-brand acquisition. Identify existing-customer support and training intent before attributing leads to new demand." }, { "id": "education", "name": "Problem and education topics", "intent": "Early research; primarily organic thought leadership", "phrases": [ "reduce payer administrative workload", "how to prioritize payer automation", "claims operations workflow mapping", "payer automation business case", "measure administrative automation results" ], "destination": "https://hcim.com/symkey/", "watchout": "Use for educational content first. Broad informational demand can consume a small acquisition test without producing near-term buying conversations." } ], "intentSignals": [ { "signal": "Specific software, vendor, or module query", "interpretation": "Potential active evaluation", "nextStep": "Align the ad and destination to the named workflow; qualify fit in the inquiry." }, { "signal": "Repeated module visits or multiple buying-group roles engaged", "interpretation": "Possible account-level interest, not a confirmed purchase decision", "nextStep": "Offer a joint operations and IT discussion, using consented first-party data and the agreed sales process." }, { "signal": "A defined workflow, owner, and implementation question in the inquiry", "interpretation": "Stronger buying evidence than an anonymous click", "nextStep": "Record the use case and qualification outcome in CRM." }, { "signal": "A general educational download or post reaction", "interpretation": "Topic interest only", "nextStep": "Nurture with relevant insight; do not count the action as a sales-qualified lead." } ] }, "negatives": { "principle": "Protect the acquisition budget by excluding demonstrated irrelevant intent at the narrowest useful scope. Review the search term and the full buyer context before adding a negative.", "plans": [ { "scope": "Shared non-recruiting acquisition campaigns", "intent": "Job seeking", "seedTerms": [ "jobs", "careers", "salary", "resume", "internship", "interview questions" ], "initialMatch": "Phrase or exact after reviewing query context", "reason": "Someone looking for employment is not shopping for payer workflow software.", "caution": "Do not apply this list to any separate recruiting campaign." }, { "scope": "Commercial software acquisition campaigns", "intent": "Academic and homework searches", "seedTerms": [ "homework", "exam answers", "assignment help", "course syllabus" ], "initialMatch": "Phrase or exact", "reason": "Exclude clearly academic assistance searches that do not indicate a buying organization.", "caution": "Do not blanket-exclude training, guide, certification, or research; a buyer may need enablement or evaluation information." }, { "scope": "Claims ad groups", "intent": "Consumer property or casualty claims", "seedTerms": [ "car accident claim", "auto insurance claim", "home insurance claim", "small claims court", "flight compensation" ], "initialMatch": "Phrase or exact", "reason": "These searches describe a different market or personal claim process.", "caution": "Avoid a broad negative such as insurance, claims, or claim status without context." }, { "scope": "Authorization ad groups", "intent": "Individual patient assistance", "seedTerms": [ "check my prior authorization", "appeal my denial", "prior authorization phone number" ], "initialMatch": "Exact or tightly scoped phrase", "reason": "A person seeking help with their own authorization is not evaluating a payer operations platform.", "caution": "Do not exclude prior authorization as a blanket phrase; some operations buyers use it when describing administrative needs." }, { "scope": "Eligibility ad groups", "intent": "Consumer benefits and assistance applications", "seedTerms": [ "am i eligible for medicaid", "apply for food stamps", "check my benefits", "unemployment eligibility" ], "initialMatch": "Exact or tightly scoped phrase", "reason": "These queries seek personal benefit eligibility rather than administrative workflow automation.", "caution": "Do not blanket-exclude Medicaid, Medicare, enrollment, or member; these can be legitimate payer contexts." }, { "scope": "Provider ad groups", "intent": "Finding personal medical care", "seedTerms": [ "doctor near me", "dentist near me", "find a primary care doctor" ], "initialMatch": "Phrase or exact", "reason": "Consumer provider discovery is different from provider-data administration.", "caution": "Do not blanket-exclude provider, directory, or network; those words can signal legitimate operations needs." }, { "scope": "New-customer non-brand acquisition only", "intent": "Existing-customer access or support", "seedTerms": [ "symkey login", "hcim support number", "symkey password reset" ], "initialMatch": "Exact", "reason": "Keep customer-support activity distinct from new-customer acquisition.", "caution": "Retain a suitable organic or support route and do not apply to dedicated customer education campaigns." } ], "doNotAutoExclude": [ "free", "comparison", "pricing", "cost", "review", "training", "Medicaid", "Medicare", "provider", "claims", "prior authorization" ], "reviewCadence": "Review search terms on each business day during the first week, then at least twice weekly during the test. Record the query, reason, scope, match choice, and reviewer in a change log.", "matchingNote": "Positive and negative matching do not behave identically. Check current platform behavior and explicitly review variants before assuming a negative covers every related query.", "successMeasure": "A declining share of spend on irrelevant terms and a healthier qualified-inquiry mix, without removing relevant buying queries or forcing an artificially low CPC." }, "strategy": { "title": "Thought leadership that earns an operations conversation", "positioning": "HCIM helps payer operations teams evaluate and automate repeatable administrative workflows with SymKey. The editorial job is to make the operational problem, the practical starting point, and the evaluation criteria clear.", "pointOfView": "Start with the workflow, not the technology label. Automation becomes useful when the team can explain what should happen, what needs human judgment, who owns exceptions, and how improvement will be measured.", "businessGoal": "Earn qualified conversations with payer organizations that have a concrete administrative workflow to improve, and equip the buying group to evaluate fit together.", "audiencePriority": "Lead with operations leaders and workflow owners; bring technical evaluators and finance partners into the same conversation through relevant proof and practical questions.", "voice": [ "Clear and specific: name the administrative work and who owns it.", "Respectful of operational complexity: distinguish repeatable steps from exceptions.", "Practical and calm: offer a useful question, checklist, or next step.", "Evidence-led: qualify claims, define denominators, and acknowledge limits.", "Human: describe what people can focus on when routine work is better organized." ], "avoid": [ "Unverified percentages, guarantees, or generic transformation claims", "Invented customer quotes, personal anecdotes, and implied endorsements", "Confusing administrative automation with medical decision-making", "Equating time released with cash savings without a valid business case", "Using conference urgency when an event has already passed", "Publishing patient information or confidential operational data" ], "pillars": [ { "id": "capacity", "title": "Capacity and the cost of repeated work", "audience": "Operations executives and team leaders", "question": "Which recurring steps consume attention that the team needs elsewhere?", "formats": [ "Short operational point of view", "Before-and-after workflow map with verified context", "A practical workload worksheet" ], "buyerStage": "Problem awareness", "cta": "Identify one recurring task worth examining." }, { "id": "workflow", "title": "Workflow-first automation", "audience": "Workflow owners and transformation leads", "question": "What can be defined, measured, and improved without trying to change everything at once?", "formats": [ "Workflow selection checklist", "One-module explainer", "Common path and exception map" ], "buyerStage": "Solution education", "cta": "Bring one process, its owner, and its rules to a discussion." }, { "id": "visibility", "title": "Visibility, ownership, and exceptions", "audience": "IT, governance, and operations stakeholders", "question": "What ran, what needs attention, and who is responsible next?", "formats": [ "Buyer questions", "Approved product walk-through", "Responsibility matrix" ], "buyerStage": "Evaluation", "cta": "Agree on the evidence and ownership needed to evaluate fit." }, { "id": "people", "title": "People, adoption, and operational change", "audience": "Managers, process owners, and enablement leads", "question": "How will the team work differently, and how will people know what to do?", "formats": [ "Operating playbook", "Training checklist", "Manager discussion prompt" ], "buyerStage": "Evaluation and implementation planning", "cta": "Define the new handoff and train for exceptions." }, { "id": "measurement", "title": "A defensible business case", "audience": "Finance, leadership, and improvement partners", "question": "What changed, what did it cost, and is the result worth expanding?", "formats": [ "Baseline template", "Measurement explainer", "Decision readout" ], "buyerStage": "Decision and expansion", "cta": "Choose the baseline and the expansion decision before launch." } ], "cadence": { "duration": "12 weeks", "weeklyPublishing": "Three LinkedIn posts: Tuesday point of view, Wednesday practical asset, and Thursday discussion or module application. Adapt to observed audience response rather than treating these days as a performance claim.", "finishedCopy": "The 12 Tuesday posts are provided in full. The calendar supplies 24 additional Wednesday and Thursday production briefs.", "monthlyDepth": "One substantive article or guide each month, broken into approved short posts and a sales conversation resource.", "engagement": "Reserve a short daily window for a subject-matter expert to answer substantive questions. Reply with useful context, not a forced demo pitch.", "distribution": "Publish from the HCIM company page and invite relevant executives or subject-matter experts to share their own approved perspective. Never attribute an authored opinion or first-person experience to an individual without their approval." }, "anchorAssets": [ { "month": 1, "title": "Which payer workflow should you automate first?", "format": "Practical guide and one-page workflow selection worksheet", "outline": [ "Name the workflow and accountable owner", "Separate common path and exceptions", "Assess repeatability, volume, friction, and business significance", "Review environment and access fit", "Define a bounded first test" ], "reuse": "A selection checklist, two short educational posts, a sales discovery aid, and a LinkedIn document post." }, { "month": 2, "title": "What to ask before an administrative workflow runs automatically", "format": "Buying-group checklist", "outline": [ "Which rules apply?", "Which actions will be logged?", "What happens to exceptions?", "Who owns access, changes, and support?", "What evidence is needed before expanding?" ], "reuse": "A buyer-question carousel, an operations/IT discussion prompt, and a follow-up resource for qualified inquiries." }, { "month": 3, "title": "From activity to evidence: measuring a payer workflow improvement", "format": "Measurement guide and readout template", "outline": [ "Document the baseline period and unit of work", "Track completion, exception, rework, and cycle time measures", "Distinguish released capacity from cash savings", "Include operating costs and ownership", "Make an explicit continue, adjust, or expand decision" ], "reuse": "A metrics explainer, a business-case discussion post, and a management review template." } ], "phases": [ { "days": "1–30", "focus": "Establish a specific, useful point of view", "actions": [ "Confirm priority buying roles, product language, and the first workflow focus", "Publish the four finished foundational posts and supporting briefs", "Build the workflow selection worksheet", "Establish tracking, campaign naming, and CRM qualification definitions", "Launch the bounded search and LinkedIn test after QA" ], "decision": "Which problems and roles produce relevant engagement and identifiable buying conversations?" }, { "days": "31–60", "focus": "Help the buying group evaluate", "actions": [ "Publish technical, visibility, and exception-handling content", "Create the buying-group checklist", "Review lead quality with sales and route follow-up by workflow", "Refresh the weakest message using observed objections", "Use approved product demonstrations or permitted evidence where available" ], "decision": "Which content and workflows bring operations, IT, and economic stakeholders into a credible evaluation?" }, { "days": "61–90", "focus": "Turn learning into decisions", "actions": [ "Publish the business-case and measurement sequence", "Produce a decision readout that distinguishes observed outcomes from assumptions", "Evaluate content-assisted opportunities using the agreed attribution view", "Retain useful topics and retire messages that create the wrong expectations", "Choose the next quarter's workflow focus from qualified pipeline feedback" ], "decision": "What should continue, change, or expand based on buyer fit and opportunity progression?" } ], "editorialWorkflow": [ { "step": "1. Brief", "owner": "Content lead with an HCIM subject-matter expert", "output": "Audience, operational problem, one point of view, source, CTA, and intended format." }, { "step": "2. Draft", "owner": "Writer or strategist", "output": "Original copy with one useful takeaway; all factual or performance claims carry an internal source reference." }, { "step": "3. Verify", "owner": "Product or operations reviewer", "output": "Confirmed product terminology, accurate capability boundaries, and permission for any customer evidence or screenshots." }, { "step": "4. Design and QA", "owner": "Creative and campaign owner", "output": "Readable mobile-first visual, accessible alt text, functioning destination, consistent message, and clean tracking." }, { "step": "5. Approve and schedule", "owner": "Authorized HCIM approver", "output": "Approved copy and creative for the relevant company or individual account; no assumed executive endorsement." }, { "step": "6. Listen and respond", "owner": "Named subject-matter expert", "output": "Useful replies, documented buyer questions, and appropriate routing for qualified inquiries." }, { "step": "7. Review and reuse", "owner": "Marketing and sales", "output": "Weekly qualitative learning and monthly funnel readout; reuse the strongest argument in a new format rather than repeating identical posts." } ], "repurposing": "Develop one strong argument into a long-form guide, a useful checklist, a short text post, a visual explanation, and a sales follow-up resource. Change the depth and purpose for each format. Preserve approved wording for factual claims.", "conferenceAssetUse": "Use approved APG graphics in a dated conference-work gallery or an explicitly retrospective article. Before using them as current promotional creative, verify event date, speakers, attendance, contact details, and any claim. Evergreen adaptations should remove outdated urgency and emphasize a useful payer-operations takeaway.", "conversionPath": "Relevant post or ad → corresponding module or educational resource → a clearly described workflow discussion → CRM qualification → held evaluation meeting → opportunity. Give the visitor a reason to take the next step at each stage.", "sources": [ { "label": "HCIM SymKey overview", "url": "https://hcim.com/symkey/" }, { "label": "Claims module", "url": "https://hcim.com/symkey-claims-module/" }, { "label": "Provider module", "url": "https://hcim.com/symkey-provider-module/" }, { "label": "Authorizations module", "url": "https://hcim.com/symkey-authorizations-module/" }, { "label": "Eligibility module", "url": "https://hcim.com/symkey-eligibility-module/" } ] }, "posts": [ { "id": "week-01", "week": 1, "title": "Start with the workflow", "pillar": "workflow", "hook": "The best first automation conversation starts with the work.", "body": "The best first automation conversation starts with the work.\n\nBefore comparing tools, name one recurring administrative process. Who owns it? What starts it? Which steps follow defined rules? Where does someone need to stop and make a judgment?\n\nThat distinction matters in payer operations. A claims queue, provider update, authorization task, or eligibility process can contain both repeatable administration and exceptions that deserve experienced attention.\n\nTrying to automate the whole problem at once makes the evaluation harder. A defined workflow creates a more useful discussion: these are the rules, this is the boundary, and this is the evidence we need.\n\nSymKey supports administrative workflows across claims, provider, authorizations, and eligibility. The practical starting point is understanding where it fits your operation.\n\nWhich recurring workflow would your team put on the whiteboard first?", "objective": "Invite a relevant operations discussion; route product questions to the matching module.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-02", "week": 2, "title": "Make capacity visible", "pillar": "capacity", "hook": "A full queue does not tell you where the effort goes.", "body": "A full queue does not tell you where the effort goes.\n\nTo understand capacity, look inside a typical unit of work. Separate active processing from waiting, checking, re-entering information, and passing the task to someone else.\n\nThen ask a harder question: which repeated steps are necessary, and which exist because the process has never been reconsidered?\n\nThat is a more useful starting point than assuming every delay needs more staff or every task needs automation.\n\nFor payer teams, a small workflow map can reveal where clearly defined administrative steps consume attention that could support exceptions and more complex work.\n\nThe goal is to build an honest baseline, not an impressive savings estimate. Measure the current process first. Decide what a meaningful improvement would look like before changing it.\n\nWhat does your team measure today: the size of the queue, or the work required to move it?", "objective": "Ask readers to distinguish queue volume from effort and encourage a baseline conversation.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-03", "week": 3, "title": "Choose a useful first workflow", "pillar": "workflow", "hook": "Your first automation workflow does not have to be your biggest problem.", "body": "Your first automation workflow does not have to be your biggest problem.\n\nIt should be a problem you can define well enough to learn from.\n\nLook for a process with recurring work, understandable business rules, an accountable owner, and a practical way to observe the result. Include the exceptions in the conversation rather than discovering them after launch.\n\nA workflow with unclear ownership or constantly changing rules may need process work before it is ready for automation.\n\nFor a payer operations team, a useful selection discussion brings the people doing the work together with the people responsible for the system. Both perspectives matter.\n\nWrite down what is included, what is excluded, and what would make the first test worthwhile. That short brief can prevent a much longer disagreement later.\n\nWhich matters most in your next workflow decision: volume, repeatability, risk, or readiness?", "objective": "Invite readers to prioritize a workflow and request a scoped evaluation if relevant.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-04", "week": 4, "title": "Protect attention for exceptions", "pillar": "capacity", "hook": "Experienced claims teams should not have to spend all their attention on the routine.", "body": "Experienced claims teams should not have to spend all their attention on the routine.\n\nTheir judgment matters when a case needs investigation, clarification, or an exception to the common path. Repeated administrative steps compete for that same attention.\n\nA useful automation discussion separates the two. What follows a defined rule? What requires review? How will the next person know what happened?\n\nThat is a more precise conversation than asking whether an entire claims function can be automated.\n\nSymKey's Claims module is one option to explore for repeatable claims administration. The right evaluation starts with your workflow and business rules, then examines the actions, boundaries, and handoffs.\n\nThe question is not simply how much work can run. It is whether the right work reaches the right person with enough context to act.\n\nWhere does your claims team most often lose that context?", "objective": "Connect the operational issue to a claims workflow discussion.", "destination": "https://hcim.com/symkey-claims-module/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-05", "week": 5, "title": "Define the exception path", "pillar": "visibility", "hook": "The exception path deserves as much attention as the happy path.", "body": "The exception path deserves as much attention as the happy path.\n\nA workflow demonstration often follows the cleanest example. An operational evaluation needs to ask what happens when the information is incomplete, a rule does not apply, or a step cannot finish.\n\nWho notices? Where does the work go? What context does the reviewer receive? Who decides whether it can run again?\n\nThese questions are especially useful when multiple teams share a payer workflow. A task can be technically complete while the next person is still unsure what to do.\n\nWrite the exception path into the operating plan. Make ownership visible. Train the people who will receive the handoff.\n\nAutomation should make responsibilities easier to understand, not leave the team guessing about who acts next.\n\nWhat is one exception your team would insist on testing before a workflow goes live?", "objective": "Start a practical conversation with operations and IT reviewers.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-06", "week": 6, "title": "Ask for visible actions", "pillar": "visibility", "hook": "A useful automation question is simple: can we see what happened?", "body": "A useful automation question is simple: can we see what happened?\n\nFor operations teams, visibility helps answer practical questions. Did the task run? What action was taken? What needs another look? Who owns the next step?\n\nThose questions belong in the evaluation, alongside workflow fit and business rules. They should not be left until someone is trying to reconstruct an issue.\n\nSymKey logs the actions it performs. In a product discussion, ask to see how those logs relate to the workflow your team wants to improve and the review responsibilities your organization needs.\n\nA log is useful when people know how to interpret it and what to do next. Define that operating process as carefully as the automated steps.\n\nWhat information would your team need in order to review a workflow confidently?", "objective": "Invite a product-specific discussion of action visibility and review needs.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-07", "week": 7, "title": "Treat provider maintenance as a workflow", "pillar": "workflow", "hook": "Provider administration is a workflow problem before it is a workload number.", "body": "Provider administration is a workflow problem before it is a workload number.\n\nA count of outstanding updates does not explain why work repeats, which rules apply, or where handoffs become unclear.\n\nStart by tracing a common update from request to completion. Identify the information required, the repeated steps, the review points, and the person responsible for exceptions.\n\nThat map creates a better conversation about what can be standardized and where automation may fit.\n\nSymKey's Provider module supports exploration of repeatable provider administration. The evaluation should connect the product to the actual process, rather than assuming every update follows the same path.\n\nThe goal is a process your team can explain, monitor, and improve. A smaller queue is useful, but knowing why it moves differently is what helps the improvement last.\n\nWhich provider workflow would benefit most from a clearer handoff?", "objective": "Move relevant readers toward the Provider module and a defined use case.", "destination": "https://hcim.com/symkey-provider-module/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-08", "week": 8, "title": "Keep administrative boundaries clear", "pillar": "people", "hook": "Authorization administration and clinical judgment are different responsibilities.", "body": "Authorization administration and clinical judgment are different responsibilities.\n\nA thoughtful automation discussion makes that distinction explicit.\n\nStart with the administrative workflow: the routine steps, applicable business rules, required information, and handoffs. Then identify the points where qualified human review is required and who owns that review.\n\nClear boundaries make the evaluation more useful for operations, technical, and clinical stakeholders. They also help prevent a broad technology claim from obscuring the actual job to be done.\n\nSymKey's Authorizations module is relevant to a conversation about repeatable administrative work. Bring the specific workflow and its review requirements to that conversation.\n\nThe objective is to support the people responsible for the process with a clearer way of working, not to blur accountability.\n\nWhich administrative step creates the most friction around your team's authorization workflow?", "objective": "Invite a bounded administrative-workflow discussion without implying automated clinical decisions.", "destination": "https://hcim.com/symkey-authorizations-module/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-09", "week": 9, "title": "Build ownership into eligibility work", "pillar": "people", "hook": "Eligibility work needs a clear owner at every handoff.", "body": "Eligibility work needs a clear owner at every handoff.\n\nWhen a routine task encounters missing information or an exception, the next step should not depend on someone remembering an unwritten process.\n\nMap who starts the work, which rules guide the routine path, what makes a case different, and who decides what happens next.\n\nThat exercise is useful before any technology decision. It also gives the team a concrete basis for evaluating automation.\n\nSymKey's Eligibility module provides a starting point for discussing repeatable eligibility administration in a payer environment. The fit depends on the workflow, the business rules, and the operating responsibilities around it.\n\nA successful change needs more than an automated step. It needs a team that understands the new process and can respond when the routine path does not apply.\n\nWhere would clearer ownership make the biggest difference in your eligibility workflow?", "objective": "Connect eligibility workflow owners with a relevant module discussion.", "destination": "https://hcim.com/symkey-eligibility-module/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-10", "week": 10, "title": "Make training part of the change", "pillar": "people", "hook": "A new workflow needs a new operating habit.", "body": "A new workflow needs a new operating habit.\n\nIf the team only learns which button to press, important questions remain unanswered. What should people check? Which exceptions need attention? When should they escalate? Who can change a rule?\n\nBuild training around those real decisions, not just a product tour.\n\nGive the team a simple operating guide: what runs, what people review, where issues go, and who owns updates. Walk through both a routine example and an exception.\n\nFor payer operations, this connects the technical change to the daily responsibilities that make it useful. It also gives managers a practical way to reinforce the process after launch.\n\nThe work is not finished when a workflow runs once. The next question is whether the people responsible for it can operate it confidently.\n\nWhat would you add to a first-week workflow training checklist?", "objective": "Generate practical discussion around adoption and operational readiness.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-11", "week": 11, "title": "Measure the operational change", "pillar": "measurement", "hook": "Time released is valuable. It is not automatically cash saved.", "body": "Time released is valuable. It is not automatically cash saved.\n\nA credible automation business case explains both the operational change and what the organization can do with it.\n\nStart with a defined unit of work and a baseline period. Track the measures that matter for the workflow: completion, waiting, exceptions, rework, or staff effort. Use consistent definitions before and after the change.\n\nThen include the cost of operating and maintaining the new process. Ask whether the result creates usable capacity, better service, or another outcome the business values.\n\nAvoid converting every minute into a savings claim without checking the assumptions. Finance and operations should be able to examine the same logic.\n\nA clear measurement plan makes the next decision easier: continue, adjust, or expand.\n\nWhat evidence would your organization need before approving another workflow?", "objective": "Invite a business-case conversation with operations and finance together.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." }, { "id": "week-12", "week": 12, "title": "Expand because the evidence supports it", "pillar": "measurement", "hook": "The next workflow should earn its place in the plan.", "body": "The next workflow should earn its place in the plan.\n\nAfter an initial change, pause long enough to ask what actually improved. Did the team gain useful capacity? Are exceptions manageable? Can people explain what ran and what needs attention? Is the process being maintained as intended?\n\nExpansion is a decision, not the default ending of a pilot.\n\nBring operations, technical, and business stakeholders back to the original goal. Compare the result with the baseline, include the costs, and document what still needs work.\n\nThen choose the next workflow using what the team has learned. A repeatable approach to evaluation is more valuable than a growing list of disconnected automations.\n\nFor a SymKey discussion, bring the workflow, its owner, and the question you need to answer. That is a practical starting point.\n\nWhat would make your team ready to expand?", "objective": "Offer a defined next conversation based on workflow readiness and evidence.", "destination": "https://hcim.com/symkey/", "publishingNote": "Ready-to-review company-page copy. Include the destination when it serves the post's CTA; obtain the normal HCIM approval before publication." } ], "calendar": [ { "week": 1, "theme": "Make the problem specific", "primaryPostId": "week-01", "primaryPostTheme": "A workflow-first point of view", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "The one-workflow brief", "brief": "Create a one-page document with fields for the workflow, owner, trigger, routine steps, exceptions, and success measure. Show an empty reusable template, not invented customer data." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Which task belongs on the whiteboard?", "brief": "Ask operations leaders to name one recurring administrative task and what makes it frustrating. Respond with a useful scoping question; do not ask for confidential details." }, "supportingAsset": "Workflow selection worksheet" }, { "week": 2, "theme": "Understand the baseline", "primaryPostId": "week-02", "primaryPostTheme": "Capacity and repeated work", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Where effort goes", "brief": "Build a simple educational visual separating processing, waiting, re-entry, checking, and handoff time. Explain that each organization must measure its own baseline." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Queue size versus effort", "brief": "Offer three questions a team can use to understand workload beyond its queue count. Ask which measure they currently lack." }, "supportingAsset": "Baseline worksheet" }, { "week": 3, "theme": "Choose a bounded starting point", "primaryPostId": "week-03", "primaryPostTheme": "A first workflow that can teach you something", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "The selection checklist", "brief": "Create a LinkedIn document covering repeatability, owner, defined rules, exceptions, environment fit, and measurability. Explain what each criterion reveals." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Operations and IT, in the same room", "brief": "Describe what each stakeholder brings to workflow selection and invite readers to add a missing perspective." }, "supportingAsset": "Month-one practical guide" }, { "week": 4, "theme": "Connect the idea to claims", "primaryPostId": "week-04", "primaryPostTheme": "Protect attention for complex work", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Routine path and exception path", "brief": "Create a conceptual claims-administration map with clearly labeled human review. Keep it illustrative of process structure, with no fabricated client metrics or patient details." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Questions for a claims workflow review", "brief": "Publish a compact list of questions about tasks, rules, ownership, and evidence. Link to the Claims module for relevant readers." }, "supportingAsset": "Claims module overview" }, { "week": 5, "theme": "Define the exception path", "primaryPostId": "week-05", "primaryPostTheme": "What happens when the routine path does not fit?", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "The exception handoff card", "brief": "Create a reusable card with exception reason, next owner, required context, escalation route, and resolution record. Use neutral examples without sensitive data." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Test the difficult example", "brief": "Explain why a workflow evaluation should include an incomplete or out-of-scope case, then ask what the team would test first." }, "supportingAsset": "Buying-group checklist, first installment" }, { "week": 6, "theme": "Make actions and ownership visible", "primaryPostId": "week-06", "primaryPostTheme": "What ran, and what needs attention?", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Five questions about action visibility", "brief": "Create a clear checklist for product evaluation: actions taken, review needs, access, operational ownership, and change handling. Product reviewers must confirm any capability statement." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "A log is only the beginning", "brief": "Discuss how review responsibilities turn logged activity into an operating process. Invite IT and operations to describe the evidence they need." }, "supportingAsset": "Approved logging walk-through or checklist" }, { "week": 7, "theme": "Apply the approach to provider work", "primaryPostId": "week-07", "primaryPostTheme": "A clearer provider workflow", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Map one provider update", "brief": "Produce an educational worksheet for request, required data, routine action, review, exception, and completion. Do not imply all provider workflows are identical." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Where does the handoff break down?", "brief": "Ask a focused question about provider administration handoffs, then offer the Provider module as a relevant next resource." }, "supportingAsset": "Provider workflow worksheet" }, { "week": 8, "theme": "Keep authorization boundaries explicit", "primaryPostId": "week-08", "primaryPostTheme": "Administrative support and human judgment", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Administrative versus review responsibilities", "brief": "Create a two-column educational document showing questions to ask about routine administrative work and qualified human review. Have the appropriate HCIM reviewer check the distinctions." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "A better authorization evaluation brief", "brief": "Explain the information to bring to a workflow conversation: administrative scope, rules, handoffs, exceptions, and review owner." }, "supportingAsset": "Month-two buying-group checklist" }, { "week": 9, "theme": "Connect ownership to eligibility", "primaryPostId": "week-09", "primaryPostTheme": "Make the next owner visible", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "The eligibility handoff checklist", "brief": "Create a short checklist for task trigger, source information, rule, exception, owner, and completion. Link relevant readers to the Eligibility module." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "The unwritten process question", "brief": "Ask what happens when the usual process expert is unavailable. Offer documentation and clear responsibility as practical starting points." }, "supportingAsset": "Eligibility process-owner worksheet" }, { "week": 10, "theme": "Prepare the people doing the work", "primaryPostId": "week-10", "primaryPostTheme": "Training for operating decisions", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "The first-week operating guide", "brief": "Produce a reusable outline: what runs, what to review, where exceptions go, who owns changes, and how to get help. Avoid promising a particular support arrangement." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Teach the exception, too", "brief": "Describe why an enablement session should include a routine example and a difficult case. Invite managers to share the most useful training question." }, "supportingAsset": "Workflow training checklist" }, { "week": 11, "theme": "Build a defensible business case", "primaryPostId": "week-11", "primaryPostTheme": "Time released and business value", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Measure before, measure after", "brief": "Create a template for baseline period, unit of work, volume, effort, exception rate, operating costs, and limitations. Clearly distinguish measured values from assumptions." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "Capacity is not the same as cash", "brief": "Explain the difference using a qualitative example, then ask what the business needs to do with released capacity for it to become valuable." }, "supportingAsset": "Month-three measurement guide" }, { "week": 12, "theme": "Decide what deserves expansion", "primaryPostId": "week-12", "primaryPostTheme": "Expand from evidence", "secondPost": { "day": "Wednesday", "format": "Document, checklist, or educational visual", "title": "Continue, adjust, or expand", "brief": "Create a management-readout template with original goal, observed change, costs, remaining issues, next decision, and owner. Do not insert invented results." }, "thirdPost": { "day": "Thursday", "format": "Discussion or module application", "title": "The next workflow conversation", "brief": "Invite relevant teams to bring a defined workflow and its owner to an HCIM discussion. Summarize the quarter's practical questions rather than claiming campaign outcomes." }, "supportingAsset": "Decision-readout template" } ], "measurement": { "principle": "Measure the quality and progression of business conversations. Clicks and reactions describe activity; they do not, by themselves, establish revenue or operational value.", "definitions": [ { "metric": "Ad spend", "definition": "The media cost reported by the advertising platform for the defined period.", "use": "Keep separate from creative, implementation, software, and agency costs." }, { "metric": "CTR", "definition": "Ad clicks ÷ ad impressions × 100.", "use": "Diagnose whether the message earns attention in its audience and placement. Do not treat high CTR as evidence of buyer fit." }, { "metric": "CPC", "definition": "Ad spend ÷ ad clicks.", "use": "Understand the price of traffic while checking the search-term and audience mix." }, { "metric": "Inquiry conversion rate", "definition": "Valid inquiries ÷ attributable landing sessions × 100, using a consistent measurement source.", "use": "Assess the offer and page experience; deduplicate spam and repeated submissions." }, { "metric": "Qualified inquiry", "definition": "An inquiry from a relevant organization and role with a concrete workflow need that meets agreed sales-fit criteria.", "use": "Record the workflow, buying role, fit, owner, and next step in CRM. A form submission is not automatically qualified." }, { "metric": "Cost per qualified inquiry", "definition": "Ad spend ÷ unique attributable qualified inquiries.", "use": "Compare campaigns on useful demand rather than raw lead count." }, { "metric": "Held evaluation meeting", "definition": "An attended meeting in which the relevant stakeholders discuss workflow fit and a real next step.", "use": "Separate booked meetings from held meetings and record the reason for no-shows or disqualification." }, { "metric": "Qualified pipeline", "definition": "The value of opportunities meeting an agreed sales-stage definition and linked to the campaign under a documented attribution rule.", "use": "Report stage, age, and source alongside value. Pipeline is not booked revenue or ROAS." }, { "metric": "ROAS", "definition": "Attributed recognized revenue ÷ ad spend, using a stated attribution model, window, and revenue basis.", "use": "Report only when revenue can be reliably connected and the sales cycle has had time to mature. Do not present projected lifetime value as realized revenue." }, { "metric": "Acquisition economics", "definition": "Evaluate gross profit and total acquisition cost in addition to media-only ROAS.", "use": "A high media ROAS can still hide an unprofitable acquisition once delivery, sales, creative, and service costs are included." }, { "metric": "Content-assisted progression", "definition": "Documented engagement with a resource by a contact or account that later advances, subject to consent and tracking limits.", "use": "Treat the content as an observed touchpoint, not proof that it caused the opportunity." } ], "tracking": [ "Use consistent campaign, ad-group, creative, and workflow identifiers in UTMs.", "Capture landing-page source and campaign fields with consent and test the form-to-CRM handoff.", "Deduplicate inquiries and maintain clear new-customer versus existing-customer classification.", "Record disqualification reasons and the requested workflow so marketing can improve targeting.", "Import qualified offline milestones only when permissions, consent, and platform requirements are satisfied.", "Reconcile platform, analytics, and CRM totals; explain attribution and timing differences rather than forcing a match." ], "reviews": [ { "cadence": "Each business day during launch week", "focus": "Spend pacing, tracking health, broken destinations, irrelevant queries, spam, and urgent lead routing." }, { "cadence": "Twice weekly during the test", "focus": "Search-term quality, audience fit, creative response, inquiries, frequency, and evidence of landing-page friction." }, { "cadence": "Weekly with sales", "focus": "Qualification, held meetings, objections, workflow needs, and follow-up quality." }, { "cadence": "Monthly and again after the normal sales cycle", "focus": "Opportunity progression, attributable revenue where available, costs, and the decision to continue, adjust, or expand." } ], "pauseRules": [ "Pause immediately for broken tracking, a failed form, a wrong destination, a material claim error, or an audience mismatch that is clearly wasting spend.", "Exclude a clearly irrelevant search term at the narrowest appropriate scope after reviewing the context.", "Set an agreed cost-per-qualified-inquiry ceiling before launch. If a campaign consumes its pre-approved diagnostic allowance without useful inquiries, investigate query quality, offer, page, and tracking before spending more.", "When responses are relevant but not converting, diagnose the handoff and offer before assuming the audience is wrong.", "Treat low-volume results as directional. Do not declare a creative winner from one conversion or an arbitrary number of days." ], "scaleRules": [ "Confirm that measurement and sales follow-up are working and that inquiries meet the agreed qualification criteria.", "Look for repeatable evidence across more than one reporting period, plus sufficient available relevant demand.", "Expand the strongest workflow and message in a controlled budget step, then reassess cost, quality, frequency, and team capacity after allowing for reporting and conversion lag.", "Do not expand all audiences, creative, keywords, and budget simultaneously; preserve the ability to understand what changed.", "For long-cycle B2B deals, use qualified progression as an interim signal while waiting for a mature revenue cohort." ], "weeklyReadout": [ "What changed in spend, qualified inquiries, and buyer mix?", "Which workflow and message produced the most relevant conversations?", "What did the team learn from queries, objections, and follow-up?", "What is the next action, who owns it, and what evidence will inform the next decision?" ] }, "budget": { "label": "Proposed 30-day media test — planning allocation, not historical spend", "currency": "USD", "total": 6000, "durationDays": 30, "purpose": "Learn which payer workflows and messages attract relevant buying conversations. This is a bounded learning budget, not a guaranteed minimum for impact or a promised revenue result.", "excludes": [ "Creative production", "Landing-page development", "Tracking implementation", "Agency or management fees", "Sales follow-up", "Taxes and any applicable platform charges beyond the media allocation" ], "channels": [ { "channel": "Google Search", "amount": 4000, "dailyAverage": 133.33, "role": "Capture explicit workflow and software evaluation intent.", "allocation": [ { "name": "Claims", "amount": 1800 }, { "name": "Provider", "amount": 900 }, { "name": "Authorizations", "amount": 700 }, { "name": "Eligibility", "amount": 600 } ], "note": "These are starting planning amounts, not rigid account settings. If available demand is thin, consolidate around the strongest validated workflow instead of forcing four underfunded ad groups. Review any brand spend separately." }, { "channel": "LinkedIn", "amount": 2000, "dailyAverage": 66.67, "role": "Reach the operations and technical buying group with a clear, useful point of view.", "allocation": [ { "name": "Qualified-role or account prospecting", "amount": 1400 }, { "name": "Engaged-audience follow-up, if viable", "amount": 600 } ], "note": "Use the follow-up allocation only if audience size, consent, and platform requirements support delivery. Otherwise keep the full LinkedIn allocation in the primary qualified audience. Begin with two message variants; do not fragment a small budget across every role and format." } ], "experiment": { "hypothesis": "Specific workflow problems and clear administrative benefits will produce a higher share of qualified inquiries than broad automation language.", "primaryOutcome": "Unique qualified inquiries and their cost, with held evaluation meetings as a downstream quality check.", "secondaryOutcomes": [ "Relevant search-term share", "Landing-page inquiry rate", "Engagement from intended buying roles", "Held-meeting rate", "Documented objections and workflow demand" ], "control": "Compare one meaningful message change at a time within a consistent audience, offer, destination, and measurement setup.", "limits": "Thirty days may reveal message and demand quality but can be too short to establish revenue ROAS for a payer software sale. Search inventory and target-account reach may also limit delivery." }, "illustrativeMath": { "label": "Illustrative arithmetic only — assumptions, not a forecast or HCIM results", "assumptions": [ "Google: $4,000 at an assumed $20 CPC produces 200 clicks.", "LinkedIn: $2,000 at an assumed $10 CPC produces 200 clicks.", "If 3% of those 400 clicks became valid inquiries, that would be 12 inquiries.", "If 50% met the agreed qualification criteria, that would be 6 qualified inquiries.", "$6,000 ÷ 6 qualified inquiries = $1,000 media cost per qualified inquiry." ], "equations": [ "Clicks = channel spend ÷ assumed CPC", "Inquiries = clicks × assumed inquiry rate", "Qualified inquiries = inquiries × assumed qualification rate", "Cost per qualified inquiry = media spend ÷ qualified inquiries" ], "interpretation": "None of these CPCs or conversion rates has been validated in an HCIM advertising account. Replace the assumptions with observed data; different inputs can produce substantially different outcomes. Click-based arithmetic is simplified and does not replace session-based analytics.", "roasExample": "If a mature campaign cohort eventually generated $18,000 of attributable recognized revenue from $6,000 in media spend, media ROAS would be 3.0×. This is an arithmetic example only, not an HCIM result or revenue expectation. Profitability requires the full cost picture." }, "beforeLaunch": [ "Confirm sales geography, priority organization types, core-environment fit, and buyer roles.", "Validate keyword availability and platform audience size.", "Approve the actual offer, destinations, ad copy, visuals, and follow-up owner.", "Test conversion events, CRM routing, qualification fields, and campaign tracking.", "Agree on the allowable learning loss, qualification criteria, and review dates." ], "expectedLearning": "A defensible view of relevant demand, message response, qualification quality, and the next test. No lead count, closed revenue, or ROAS is guaranteed." } }