Defensible by designDecisions remain reviewable and evidenced.
Transparent processScope, ownership and boundaries stay visible.
Client-first partnershipWork starts with the operating need.
Secure by defaultAccess and sensitive data stay controlled.

Case studies & evidence

What changed, what was measured, and what the evidence actually supports.

These case studies cover client work, internal product engineering and confidential technical engagements. Metrics are published only when they can be tied to a source or documented project result. Client identities are withheld where NDA or contractual confidentiality applies.

Illustration of documented project evidence, verification and rollback planning
Concept illustration — not a client screenshot or claimed project result.

Measured work

Results without invented attribution.

Search visibility is not presented as revenue. Engineering capability is not presented as a guaranteed outcome. Confidential work stays confidential. Each case makes those boundaries visible.

Measured internal case studySEO, web platform and measurement

Lancaster Solutions: building a measurable search and web platform

A production Django platform was hardened around performance, security, accessibility, structured data, search measurement and conversion instrumentation while its organic footprint expanded.

7,368 Search impressions
59 Organic clicks
+121% 28-day impression growth
32.57 → 29.90 Average position

What the work covered

  • Django public platform architecture and production operations
  • Technical SEO, canonicals, robots, sitemap and structured-data controls
  • Mobile-first performance, accessibility and static-asset optimization
  • Search Console analysis and first-party conversion measurement

Supported outcome

Lancaster Solutions now operates a measurable search and web platform with a substantially larger organic footprint, stronger average positioning and explicit conversion/CTR diagnostics instead of relying on traffic growth as the only success signal.

Read the evidence
Active measured experimentTechnical SEO and controlled experimentation

Winchester, Virginia: isolating a SERP click-through constraint

Lancaster held the landing-page body, H1, URL and schema stable while changing only the primary title and meta description, allowing the SERP treatment to be evaluated as a controlled variable.

1,748 Page impressions
342 Exact-query impressions
14.18 Exact-query avg. position
1 Page click in export

What the work covered

  • Search Console query/page diagnosis
  • Controlled title and meta-description treatment
  • Stable H1, body copy, URL, schema and CTA architecture
  • GA4/first-party measurement hooks for Winchester organic landings

Supported outcome

A ranking-versus-click problem was converted into a controlled, production-verified SERP experiment with clear baseline evidence and privacy-aware measurement.

Read the evidence
Live product engineering and search case studySaaS, technical auditing, SEO education and search discovery

Asuruas: from audit and SEO tooling to live SaaS and a public learning system

Asuruas evolved through several stages—from repeatable audit/SEO tooling, to governed website intelligence, to a multi-tenant SaaS product, and then into a combined software-and-learning system with a large public technical SEO knowledge surface.

1,375 Search impressions
5 Organic clicks
194 URLs in page report
2.77 Homepage avg. position

What the work covered

  • Authorised, bounded crawling and public-target safeguards
  • Technical SEO, accessibility, performance, security, content and quality observations
  • Evidence, severity, confidence, limitations, ownership and remediation workflows
  • Multi-tenant organisation and individual account architecture

Supported outcome

A multi-year audit and SEO operating method became a live multi-tenant SaaS product and public SEO learning system, with early measurable organic discovery and a governed process for continuing search optimization without losing attribution.

Read the evidence
Client case studyWeb development, technical SEO and managed operations

Ramsay Resilience Group: building a searchable managed web foundation

Lancaster developed the site structure, service content, technical SEO, security and managed delivery model, then used Search Console data to identify where service visibility was emerging.

829 Search impressions
18 Organic clicks
4.00% Homepage CTR
3.96 Services avg. position

What the work covered

  • Information architecture and service-page development
  • Copy development and source-material restructuring
  • Technical SEO, titles, metadata and internal linking
  • Analytics and conversion foundations

Supported outcome

Ramsay Resilience Group gained a managed web platform with distinct service-search surfaces, measurable organic visibility and an ongoing technical ownership model.

Read the evidence
Measured client case studyWebsite, local SEO and managed hosting

Always Best Solutions: early local-search traction in a shortened measurement window

The available Search Console window shows early organic traction and especially strong mobile click-through, but the site later went offline, preventing a normal long-term measurement period.

217 Search impressions
11 Organic clicks
5.07% Overall CTR
19.15% Mobile CTR

What the work covered

  • Website build and service-page structure
  • Technical SEO and metadata
  • Performance-oriented hosting foundation
  • Local-service search targeting

Supported outcome

The active measurement period produced measurable local-search visibility, an overall 5.07% organic CTR and notably strong mobile engagement before the site's public measurement window ended.

Read the evidence
Internal engineering case studyDjango, infrastructure and release engineering

Production engineering: making application readiness stricter than process state

Two acceptance failures were safely rejected and used to harden deployment gates around HTTP readiness, dependency restoration, stable worker PIDs, rollback snapshots and exact source qualification.

Public stable responses
Additional stability probes
2 Failure modes caught
0 Schema changes

What the work covered

  • Exact Git SHA and file-scope qualification
  • Rollback snapshots before production writes
  • Django checks and migration-drift validation
  • Serialized service transitions

Supported outcome

Production acceptance now depends on observable application behavior and critical-service stability, with automatic rollback evidence when those conditions are not met.

Read the evidence
Internal product/operations case studyCRM and internal application engineering

Mobile sales operations: shortening the path from lead to follow-up

Lancaster built a mobile sales queue around one-tap contact/research actions, audit and enrichment workflows, assignment, fit scoring and a growing compliance model for opt-outs, DNC and no-solicitation handling.

44–48px Mobile action targets
2 Primary mobile queues
1 tap Google lead research
5/5 Critical services active

What the work covered

  • Priority lead and opportunity queues
  • Click-to-call and email actions
  • Google lead lookup using company/location/phone context
  • Lead enrichment and website/audit workflows

Supported outcome

The internal CRM now provides a production-verified mobile research/contact workflow and a foundation for a more complete employee sales operating system.

Read the evidence
Confidential experience case studyWeb operations, hosting and white-label delivery

Operating at scale: 248 websites under simultaneous personal responsibility

At peak scope, Curtis Lancaster personally handled 248 websites simultaneously, requiring repeatable practices for maintenance, hosting, DNS, SSL, backups, security, performance, SEO, migrations and incident response.

248 Websites simultaneously handled
1 Accountable operator
Multiple Delivery models
Repeatable Operations model

What the work covered

  • WordPress/application maintenance
  • Hosting, DNS, SSL and email troubleshooting
  • Backups, restore planning and incident response
  • Security and plugin/theme risk management

Supported outcome

A high-volume web operations workload was managed through increasingly standardized maintenance, recovery and diagnostic practices that later informed Lancaster Solutions' operating model.

Read the evidence
Confidential client case studyPerformance engineering

Performance recovery: reducing an approximately eight-second load to under two seconds

The delivery path was diagnosed across hosting, caching, assets, WordPress/application behavior and rendering rather than assuming the visual design itself was the root cause.

~8s Starting load time
<2s Post-work load time
>75% Load-time reduction
End-to-end Delivery analysis

What the work covered

  • Server/hosting response review
  • Caching and delivery-path analysis
  • Image and static-asset optimization
  • Plugin/application overhead review

Supported outcome

Load time was reduced from approximately eight seconds to under two seconds, an improvement greater than 75%.

Read the evidence
Confidential client case studyMigration, web development and incident delivery

Emergency five-page migration and redesign completed in an approximately 17-hour response window

A five-page site was migrated and redesigned through a concentrated recovery workflow that accounted for content preservation, hosting, DNS/SSL, mobile behavior and launch verification.

5 Pages
~17h Response window
1 Controlled migration
Verified Launch state

What the work covered

  • Content preservation and page reconstruction
  • Hosting migration
  • DNS and SSL considerations
  • Responsive redesign

Supported outcome

The five-page migration and redesign was completed within the approximately 17-hour emergency response window.

Read the evidence
Confidential product/operations case studyFlask, monitoring and operations automation

Monitoring and automated recovery: moving beyond ‘the site is down’

A Flask-based monitoring system was developed around uptime verification, keyword/content checks, dashboards, alerting and automated recovery concepts.

Detect Stage 1
Diagnose Stage 2
Recover Stage 3
Verify Stage 4

What the work covered

  • Flask monitoring application development
  • Uptime and content/keyword verification
  • Operational dashboards
  • Alerting workflows

Supported outcome

The project established practical monitoring and recovery patterns that later informed more governed operational products and managed-service workflows.

Read the evidence
Product engineering case studySaaS, monitoring and recovery engineering

Phoenix and Sentinel Cove: governed recovery and operational visibility

Sentinel Cove and Phoenix were designed as complementary operational layers: visibility and incident ownership on one side, approval-aware diagnosis/recovery/verification on the other.

5 Governed recovery stages
Least privilege Credential model
Explicit Human responsibility
Auditable Incident evidence

What the work covered

  • Website/service monitoring views
  • Incident timelines, acknowledgement and ownership
  • Independent health verification
  • Action allowlists and approval roles

Supported outcome

The products establish a governed operating model for monitoring and recovery that keeps evidence, permissions and human responsibility visible.

Read the evidence

Publication standard

Useful proof without exposing clients or manufacturing numbers.

Named clients appear only where the relationship can be discussed publicly. Other work is described by the technical problem and supported outcome, with the identity withheld under NDA or contractual confidentiality.

Know what to fix first

Get a clear review of the website, visibility and follow-up.

We will separate urgent problems from useful improvements and recommend the smallest sensible next step—without pretending every site needs a full rebuild.

CallFree reviewFind a starting point