Dreiling Chiropractic
Custom One-Page Business Website
A custom one-page website built to clarify a walk-in-only chiropractic model and establish a new online presence.
Implementation Focus
What I implemented
Handled full project lifecycle including discovery, design direction, frontend development, content structuring, integrations, and deployment for a client website under tight constraints.
Problem
The business had no website under its new name, and customers were confused about whether it was the same chiropractor and how the clinic operated. The most critical issue was that the clinic was walk-in only, but customers were still attempting to schedule appointments or call unnecessarily.
Approach
Designed and built a custom one-page website focused on clarity, trust, and reducing friction. Structured the entire page around answering common customer questions up front, emphasizing the walk-in model, and reinforcing continuity of care under the new business name.
Outcome
Delivered a fully responsive one-page website that clarified the walk-in model, reinforced brand continuity, and established a digital presence for the business.
Constraints
- One-month delivery timeline
- Extremely limited budget ($250 total build)
- Minimal client input during discovery
- No structured requirements or documentation provided
- Limited access to owner for feedback (would not meet outside business hours)
- Inability to properly stage or retake photos
- Restrictions on branding decisions (colors, clothing, imagery)
Tradeoffs
- Built a single-page site instead of a multi-page structure due to budget constraints
- Reduced animation and interactivity to keep scope manageable
- Used available imagery despite quality limitations
- Deferred features like scheduling due to scope and technical constraints
Ownership
What I owned
Execution Breakdown
How the work was implemented
Discovery & Requirement Translation
The project required extracting requirements from minimal client input and translating them into a usable product direction.
Limited Discovery Input
Client provided minimal structured input and did not complete discovery materials, requiring interpretation of needs.
Key Business Goals
Identified that the most important goals were clarifying the walk-in model and reinforcing brand continuity.
Decision Ownership
Took ownership of layout, structure, and messaging due to lack of defined requirements.
Content & UX Strategy
The site was structured to reduce confusion and unnecessary customer interactions.
Walk-In Clarity
Positioned the walk-in model as the primary message across the page to reduce calls and scheduling confusion.
FAQ-Driven Structure
Designed sections to proactively answer common questions about services, process, and expectations.
Call Reduction Strategy
Intentionally avoided placing the phone number prominently to discourage unnecessary calls.
Technical Implementation
Built a custom static site with targeted integrations instead of using a CMS or template-based system.
Custom Frontend
Developed using React and Vite to create a lightweight, responsive site.
Google Maps Integration
Embedded location data to help users find the clinic easily.
Facebook Feed Integration
Connected live Facebook content to provide ongoing updates without requiring manual site updates.
Content Creation & Media Handling
Managed all content and media under significant constraints.
Image Capture
Captured images during live business hours without controlled lighting or staging.
Image Processing
Edited and formatted images using Canva despite quality limitations.
Copywriting
Used AI-assisted copywriting to structure messaging clearly and concisely.
Scope & Change Management
Handled post-delivery requests that were outside the original scope.
Scheduling Request
Client requested adding a scheduling system after delivery, which would have required a full redesign and new discovery process.
Technical Constraint
Explained that plugin-based solutions (e.g., Calendly) were not compatible with the custom-built architecture without additional work.
Expectation Gap
Client feedback post-delivery highlighted the importance of formal approvals and visual mockups before development.
Workflow
System flows
Website Build Flow
- 1Initial discovery conversation to understand basic needs.
- 2Second session to align on direction and tone.
- 3Defined content structure based on business goals.
- 4Built frontend layout and integrations.
- 5Captured and processed images under constraints.
- 6Deployed site and configured DNS.
User Experience Flow
- 1User lands on the website.
- 2User immediately sees walk-in messaging.
- 3User reviews FAQs and service information.
- 4User understands they do not need an appointment.
- 5User visits the clinic without calling.
Results
Impact and outcomes
Clear Business Communication
Successfully communicated the walk-in-only model and reduced confusion around scheduling expectations.
Established Online Presence
Provided the business with its first website under the new brand name.
Delivered Under Constraints
Completed the project within a short timeline and limited budget while handling unclear requirements.
Visual Proof
Screens and artifacts
Discovery
Screenshots of the discovery form.
Website Design
Screenshots of the one-page layout showing structure, messaging, and integrations.
Reflection
What I learned
What worked
- Simplified structure effectively communicated the most important information.
- Custom build allowed full control over layout and messaging.
- Integrations provided dynamic content without increasing maintenance burden.
What I’d improve
- Require signed contracts before starting work.
- Use visual mockups (Figma) before development to align expectations.
- Formalize image requirements and schedule controlled photo sessions.
- Define scope boundaries more clearly for post-delivery requests.
Key takeaway
This project reinforced that implementation is not just about building—it’s about managing ambiguity, setting expectations, and translating incomplete requirements into a working system.