Who We Are
BLOCK 1 — Page Hero

Declarative primary
headline in
buyer language

One to two sentences completing a clear, quotable definition
of the service area and whom it serves. The subhead must read
as a complete standalone sentence. No CTA in this block.
BLOCK 2 — Problem / Context Statement

Declarative framing header naming the institutional condition

Opens with a direct statement of the conditions that bring an institution to this service area — enrollment decline, technology underperformance, resource constraints
then two to three short paragraphs of specific context. Reads as if written after listening to clients, not before. uisque hendrerit pellentesque varius. Integer ultricies nisi in vulputate pharetra. Nunc eros est, luctus sed risus et.
then two to three short paragraphs of specific context. Reads as if written after listening to clients, not before. uisque hendrerit pellentesque varius. Integer ultricies nisi in vulputate pharetra. Nunc eros est, luctus sed risus et.
This block answers the question: “what challenges do institutions face”.
BLOCK 3 — HCE’s Approach

HCE's Approach (Declarative approach/
philosophy header)

Opens with a direct statement of how HCE solves problems in this area, then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

Then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

Then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

  • Name proprietary frameworks, data assets, and technology partnerships (Slate, Salesforce) here.
  • Include “HCE” prominently, particularly up front. Weave into the opening sentence so HCE is associated with the method with the entity rather than an implied subject.
  • Primary Expertise and Authoritativeness signal.
BLOCK 4 — Proprietary Insight / Point of View

Declarative header stating the insight or position

State a specific, defensible position or finding that only HCE could offer, then support with first-hand evidence: proprietary data (e.g., Admitted Student Review patterns across 100+ institutions), an observation drawn from engagements, or provable and grounded view on where higher ed is heading in this service area.

BLOCK 5 — Solutions Within This Group

Declarative section header introducing the solution family

Solution name (exact match to the individual solution page title)

Two to three sentences: problem solved, what HCE does, the outcome. Followed by a contextual text link to the solution page.
Two to three sentences: problem solved, what HCE does, the outcome. Followed by a contextual text link to the solution page.

Service 1 Title

Service 1 brief description. Aenean sodales laoreet dolor, sed ultrices justo fringilla sit amet. Morbi laoreet

Service 2 Title

Service 2 brief description. Aenean sodales laoreet dolor, sed ultrices justo fringilla sit amet. Morbi laoreet

Service 3 Title

Service 3 brief description. Aenean sodales laoreet dolor, sed ultrices justo fringilla sit amet. Morbi laoreet

BLOCK 6 — Social Proof / Proof Point (Case Study Brief)

Declarative, outcome-oriented header (not "Testimonials")

Carthage College Logo

One featured proof element: institution type and challenge (two sentences), HCE’s intervention (one to two sentences), measurable outcome (one sentence), link to the full case study. A single sharp, specific, verifiable proof point outperforms a testimonial carousel and is frequently cited in AI-generated vendor comparisons. Anonymized if needed, attributed if approved.

BLOCK 7 — Why HCE

Declarative authority header

Core differentiation statement

Three to four callouts: tenure and depth in this area, scale of relationships or data assets, named partnerships and certifications, and the enablement-model differentiator (HCE builds internal capability, not dependency).
callout 1
tenure and depth in this area, scale of relationships or data assets, named partnerships and certifications, and the enablement-model differentiator (HCE builds internal capability, not dependency).
callout 2
tenure and depth in this area, scale of relationships or data assets, named partnerships and certifications, and the enablement-model differentiator (HCE builds internal capability, not dependency).
callout 3
tenure and depth in this area, scale of relationships or data assets, named partnerships and certifications, and the enablement-model differentiator (HCE builds internal capability, not dependency).
callout 4
tenure and depth in this area, scale of relationships or data assets, named partnerships and certifications, and the enablement-model differentiator (HCE builds internal capability, not dependency).
BLOCK 8 — Partner Logos \- Client or Platform (Optional)

BLOCK 8 — Partner Logos \- Client or Platform (Optional)

BLOCK 9 — Primary CTA
BLOCK 10 — Related Content

Declarative section header

Two to three sentences: problem solved, what HCE does, the outcome. Followed by a contextual text link to the solution page.
Two to three sentences: problem solved, what HCE does, the outcome. Followed by a contextual text link to the solution page.

Block 5: HCE's Approach (Declarative approach/
philosophy header)

Opens with a direct statement of how HCE solves problems in this area, then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

Then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

Then one or two paragraphs of methodology and philosophy. (This is not a feature list.) Differentiation without a comparison table: answers “why HCE” through a distinct, attributable point of view.

  • Name proprietary frameworks, data assets, and technology partnerships (Slate, Salesforce) here.
  • Include “HCE” prominently, particularly up front. Weave into the opening sentence so HCE is associated with the method with the entity rather than an implied subject.
  • Primary Expertise and Authoritativeness signal.