Service Page Creation Guide for LLMs

This guide provides comprehensive instructions for creating professional service pages for Barry Hennessy’s consulting website. Use this to understand the context, structure requirements, and quality standards for generating new service offerings.

IMPORTANT: Always read content/plans/AGENTS.md FIRST for site-wide guidelines on SEO, pricing, tone, quality standards, and brand positioning before using this service-specific guide.

🎯 Service-Specific Context

Global Context: See content/plans/AGENTS.md for complete site-wide brand positioning, target audiences, and business context.

Service Page Purpose

Service pages serve three primary functions:

Lead Generation: Convert visitors into qualified prospects through clear value propositions
Credibility Building: Demonstrate deep technical expertise and thought leadership
Decision Support: Help potential clients evaluate fit and make informed purchasing decisions

Service-Specific Audience Focus

Primary: Engineering leaders needing strategic technical guidance
Secondary: Development teams requiring implementation support
Buying Triggers: System scaling issues, architecture debt, team productivity challenges

🏗️ Service Page Structure & Decisions

Core Decision Framework

1. Service Definition

Decisions to Make:

What specific problem does this service solve?
Who is the ideal client profile?
What are the measurable outcomes?
How does this differ from existing services?

High-Level Goals:

Clearly articulate the value proposition
Position against competitors in the space
Create desire for the specific solution offered

2. Content Structure

Decisions to Make:

What sections should be included for this specific service type?
How to balance technical depth with accessibility for target audience?
What social proof elements are most relevant?
How to handle pricing transparency for this service category?

High-Level Goals:

Guide qualified prospects through informed purchase decisions
Build trust through service-specific evidence and transparency
Create clear engagement paths appropriate to service complexity

3. Tone & Voice

Decisions to Make:

How technical should the language be?
What level of formality is appropriate?
How to balance confidence with approachability?
What storytelling elements to include?

High-Level Goals:

Connect with engineering audience
Demonstrate deep expertise
Build personal connection with Barry

Required Page Sections

Hero Section (Introduction)

Write a tight intro that states the outcome and who it is for.

## What you get
- Bullet the tangible outcomes.

## How it works
1. Step-by-step outline for delivery and collaboration.

## Packages
- Outline sprints/retainers/workshops with price hints.

## Next steps
- Mention CTA again and how to reach you.

📝 Frontmatter Template

---
title: "Service Name"
slug: "service-slug"
date: 2025-01-15
draft: false
summary: "1-2 sentence description for listings and SEO"

# Pricing and CTA
price_hint: "From €X — format description"
cta_label: "Book intro call"
cta_url: "https://booking-link"

# Service categorization
badges:
  - "Decision-Driven Design"
  - "Architecture"
service_type:
  - "decision-driven-design"
audience:
  - "eng-leads"
  - "founders"
stage: "live"  # live, beta, draft
highlight: true  # Feature on homepage

# Layout and display
layout: "services/single"

# Optional structured content
hero: "Optional hero section content"
problems: []  # Client problems addressed
promise: []   # Service promises
packages: []  # Package descriptions
faq: []       # FAQ items
---

💰 Pricing Structure & Communication

Global Pricing Strategy: See content/plans/AGENTS.md for complete pricing philosophy and structure.

Service-Specific Pricing Decisions

Decisions to Make:

Which pricing tier structure fits this service type?
How to communicate value for the price point?
What payment terms and conditions to include?
How to handle enterprise/custom pricing?

Service-Specific Goals:

Price commensurate with value delivered
Clear justification for pricing tiers
Flexible options for different client sizes
Transparent terms that build trust

Pricing Communication Standards

Always use ranges (e.g., “From €3.5k”) not fixed prices
Include timeframes (e.g., “2-5 day sprint”)
Clearly list what’s included in each tier
Explain the value proposition for each price point
Offer multiple engagement options (sprint, retainer, workshop)

🎨 Content Quality Standards

Global Standards: See content/plans/AGENTS.md for complete site-wide quality standards including SEO, technical accuracy, and writing excellence.

Service-Specific Quality Decisions

Sales Conversion Optimization

Decisions to Make:

Which pricing objections to proactively address
How to position packages against each other
What social proof elements to include
How to create appropriate urgency for different service types

Service-Specific Goals:

Convert qualified traffic (not general visitors)
Demonstrate ROI and value justification
Reduce sales cycle friction
Build long-term client relationships

Technical Credibility for Services

Decisions to Make:

How deep should technical examples go for each audience segment
What case studies or examples best demonstrate value
How to balance technical depth with accessibility
What credentials or experience to highlight

Service-Specific Goals:

Position as trusted technical advisor
Demonstrate practical experience with real challenges
Show understanding of client constraints
Build confidence in implementation capability

📋 Service Page Templates

Choose from available templates based on your service type:

Technical Consulting Services

File: template-technical-consulting.md Use for: API reviews, architecture assessments, technical audits, performance optimization Example: API Architecture Review & Design service

Methodology & Training Services

File: template-methodology-training.md Use for: Workshops, team training, coaching, framework implementation Example: Decision-Driven Development Training service

Custom Services

For services that don’t fit these templates:

Start with the appropriate template as a base
Modify frontmatter, structure, and content to fit your specific service
Maintain the core sections: What you get, How it works, Packages, Next steps
Adapt tone and technical depth to your target audience

Template files contain complete, ready-to-use examples with proper frontmatter and content structure.