Thornbury
A reference implementation of how a professional-services firm earns premium engagements online: editorial authority, structured expertise, and an inquiry flow that qualifies before it books.
- Category
- Professional services
- Discipline
- Website design and development
- Demo
- In development
- Related service
- Website Design and Development
01
Overview
What Thornbury is
Thornbury is a Kramiva reference implementation demonstrating a professional-services website for advisory, legal, and consulting firms. It explores editorial publishing, sector and practice-area pages with distinct arguments, author profiles, and a situation-based inquiry flow that qualifies before it books. It is a self-initiated build, not commissioned client work.
- The problem
- An advisory firm wins entirely on referral and has no way to turn its expertise into inbound work.
- Intended users
- Partners at consulting, legal, accounting, and advisory firms.
- Status
- Thornbury deploys to a public subdomain alongside its measured Core Web Vitals. Nothing is published as a result until it has been measured.
02
Product approach
What we decided, and what we cut.
01
Publish the thinking, not the brochure
02
Qualify before the calendar
03
Deliberately left out
03
Inside the build
The experience, and the engineering.
The main experience, step by step
- 01DiscoverArrival on a sector page or an article through search or a shared link.
- 02AssessRelated thinking, the relevant practice area, and named people with real credentials.
- 03Self-identifySituation-based entry points instead of a generic contact form.
- 04QualifyA short structured inquiry covering situation, timing, and scale.
- 05MeetA scheduled conversation with context already in the partner's hands.
Feature set
- Editorial publishing system with structured long-form layouts
- Sector and practice-area pages with distinct arguments
- Author profiles linked to their published thinking
- Situation-based inquiry routing
- Answer-engine-ready structured data across articles and practices
- Accessible, printable article layouts for how this audience actually reads
Architecture decisions
Editorial content changes rarely and must load instantly; a static page revalidated on publish gives both.
A malformed article fails the build rather than reaching production with broken structured data.
Partners draft and review without touching a repository, which is the difference between a system that gets used and one that does not.
Relevance from meaning rather than shared tags, so a reader lands on the genuinely adjacent argument.
No server to keep alive for content that changes weekly.
Technology and integrations
- Sanity
- Cal.com
- Plausible
- Resend
Measured results
Not measured yet.
Estimates presented as measurements are the most common lie on an agency website, and it is not one we are willing to tell.
Something like this, for your business.
A short brief gets you a real reply from a founder within one business day — an honest read on fit, scope, and budget.