Maggie’s brief,seen section by section.

• Do not imply the business is fully operating. The project is pre-launch. Do not say a Google profile, customer reviews, rating, team, or production site already exists.
• Daniel must choose the name from Steady Home Works, Steady Home Fixes, and Steady Home Improvements. Any name shown before that decision is only a working label.
• Do not claim name availability. No official Connecticut entity, trade-name, domain, or trademark check has been completed.
• Keep location unresolved until confirmed. The user describes the business as serving Berlin, CT; the fetched existing homepage says Kensington, CT. Confirm the accurate public location and actual service area before changing location copy or SEO.
• Keep both design options. The existing burgundy site is the baseline; the separate staged design is version B for comparison, not the chosen replacement.
• Do not invent facts. No completed jobs, customer stories, reviews, team, credentials, screening practices, prices, service capacity, operating hours, response times, or guarantees unless Daniel confirms them and can support the claim.
• Keep draft content visibly draft. The illustration is not Daniel or a real job; photo/review slots are placeholders; the preview form does not submit or save data.
• Respect the older homeowner’s choice. Speak to adult children and caregivers without excluding others; keep the older adult involved as decision-maker. Share family updates only with the homeowner’s permission and chosen contacts.
• Use plain, senior-friendly language. Keep it informative and conversational—not salesy or sassy. Avoid jargon, pressure, pity, and fear-based copy.
• Keep service claims bounded. Mark unconfirmed offerings as possible items to confirm. Clearly refer out work Daniel is not qualified, registered, insured, equipped, or prepared to do.
• Follow the plan. Before changing the business name, overall visual design, page structure, or launch scope, flag it as a plan deviation and ask first. Copy simplification and content edits within the agreed senior page are on-plan.

The table below keeps all items from the recorded Maggie coverage matrix. “Covered” means represented in the staged draft—not independently verified or ready to publish.

Audience and tone

Keep the niche as patient handyman service + practical home-safety updates for older adults and families. Do not use “cheap” as the differentiator. Use positive, verifiable process promises instead of “usual handyman vs. Daniel” attacks. When describing a walkthrough, use “non-clinical home walkthrough” or “home repair walkthrough,” not clinical risk-assessment language.

• Speak to adult children who may arrange or pay for help—especially women around 45–65—without excluding sons, other family, caregivers or the senior homeowner.
• Use larger, easy-to-read text, simple fonts, plain direct wording and clear steps. Keep the older adult’s dignity, privacy and choice central.
• Use Daniel’s real caregiving and family story only after he confirms the details. Mention patience, listening, safety concerns, his real approach and family trust without making up a credential or claim.
• Make family coordination permission-based: the homeowner decides who may join, receive photos or get updates.
• Keep language informative and conversational, not salesy or sassy. Simplify page wording without changing the agreed structure or launch scope.

Proof that must remain a placeholder until verified

Service scope and referral boundary

Competitor offerings are prompts for questions, not Daniel’s service list. Keep smart-home setup and recurring maintenance labeled as possible services to confirm. Do not imply they are available until Daniel confirms skills, support capacity, price and operating process.

Ramps, stair lifts, doorway widening, structural work, major bathroom changes and regulated electrical/plumbing trades may require specialist qualifications, registrations, insurance or permits. Mark these as referral jobs unless Daniel confirms he is qualified and equipped to take them.

The staged contact form is a non-submitting preview and must not collect real client information. Do not treat the draft page as a live lead form.

This was not a full Google Maps/SERP audit or a verification of competitors’ claims. Use these examples to discover questions and possible referral boundaries; do not copy credentials, service promises or operating practices as Daniel’s.

Seven useful themes to consider in the draft

1. Specific trust proof: who visits, the actual screening process, registration/insurance, and any real training.
2. A clear visit flow: listen, agree on the scope and price, do the work, then walk through the result.
3. Family coordination from a distance—with the homeowner’s permission and control over who gets updates.
4. Home technology and recurring maintenance as possible offerings to confirm, not automatic promises.
5. A clear “refer out” boundary for ramps, stair lifts, doorway widening, structural work, major bathroom changes and regulated trades.
6. Before/after project storytelling with permission, actual photos and what changed—without medical or fall-prevention guarantees.
7. Practical home help is for the older homeowner as well as the adult child arranging a visit.

Claims deliberately not copied

• “Certified,” “CAPS,” “Senior Home Safety Specialist,” “licensed,” “insured,” “bonded,” “ten years’ experience,” or “background-checked team” unless Daniel can document the exact claim.
• “Free assessment,” a clinical/medical safety assessment, ADA-compliant outcomes, guaranteed fall prevention, 24/7/emergency response, guaranteed appointment windows or a satisfaction guarantee unless the offer, qualification and operating process are real.
• Ramps, lifts, structural modifications, full bathroom remodels or licensed electrical/plumbing work unless Daniel has confirmed qualifications, registrations, insurance and delivery capacity.

How to compare them fairly

• Compare both using the same approved copy and the same desktop and mobile sizes.
• Check reading comfort, text resizing, contrast, navigation and calls to action.
• Check mobile layout and usability; test keyboard access, forms and screen-reader labels before launch. The research notes call for text resize to 200% without breakage, visible focus, reflow with no horizontal scrolling, contrast of at least 4.5:1 (7:1 aim), and testing with screen readers.
• The staged draft uses an 18px body base and three text-size settings (18px, 20.5px and 23px); verify the actual result at browser zoom and across devices rather than treating the control as proof of accessibility.
• Do not replace the existing design until Daniel, Maggie and the web team choose a version.

Visual reference used in this guide

To echo the available Steady Home Works burgundy direction, this HTML uses the wine/cream palette from the staged stylesheet and Merriweather/Lato typefaces identified in the project notes. The original source file is still needed to verify exact styling against the existing site.

Type: Merriweather for headings and Lato for body copy, matching the design notes for the existing burgundy direction. These fonts are embedded in this file for an offline preview.

Visual decisions to confirm

• Get the original burgundy source files or clear desktop/mobile screenshots. Verify the palette and typography against the real version A; these available notes alone do not establish an exact match.
• Compare A and B with the same approved copy; ask Daniel, Maggie and the web team which visual direction to keep before changing the production site.
• Confirm the final name before commissioning a logo or lockup. This guide’s “S” is a decorative placeholder, not a brand approval.
• Agree on real imagery, photo permissions, example-project labeling, button wording and icon treatment; do not imply the draft illustration shows Daniel’s work or a real client.
• Test real foreground/background color pairs, contrast, mobile spacing, text resizing, focus states and keyboard access. The palette by itself is not an accessibility pass.

You can add exact identity decisions and their owner/source to this section below; keep unconfirmed changes labeled as open.

• Final business name and its relationship to DMTile LLC.
• Correct public location: Berlin or Kensington; actual service radius and towns.
• Actual service list, jobs to refer out, call-back hours, phone number and schedule.
• Whether Daniel works alone or has a team; each worker/subcontractor’s role and screening process.
• Connecticut contractor/trade registrations, insurance, training and contract workflow.
• Pricing method, parts policy, travel/minimum charge, recurring visits and urgent/discharge scheduling.
• Whether family photo updates and written post-visit summaries are feasible and how permission is recorded.
• Which personal story details Daniel is comfortable publishing.
• Maggie’s approval of the copy and referral handoff, separately from her earlier soft approval of visual direction.
• Official business-name, trade-name, domain and trademark checks; none has been completed in the current project.
• The full original site files or clear desktop/mobile screenshots needed for A/B comparison.

• Daniel has selected the real-world business name; official entity/trade-name, domain and trademark checks have been made.
• Public location and only the real service areas are confirmed before location copy or SEO is changed.
• All listed services, referral limits, prices, visit fees, schedule, callback and follow-up promises are confirmed and deliverable.
• Applicable Connecticut registration, insurance, contracts and trade-scope questions are checked with Connecticut DCP or a qualified professional.
• Every claim about Daniel’s story, workers, screening, experience, training, credentials and insurance is confirmed and supported.
• Real job photos and customer words are used only when available, accurate and permitted; no sample stories or reviews remain.
• The correct Google Business Profile is created only after identity and location are settled. The profile name matches the real-world name; list only actual service areas, and hide a service-area business address if customers are not served there.
• Reviews are genuine and linked to the correct profile. Never invent, incentivize or selectively solicit positive reviews. Do not publish a rating or review count before it exists.
• Do not use self-serving review-star structured data for the business’s own LocalBusiness/Organization page.
• Daniel approves the facts; Maggie and the group approve copy, referral handoff, and final design separately.
• The staging page remains noindex; final domain, form, phone links, privacy wording, mobile layout, text controls, contrast, keyboard and screen-reader behavior are tested before launch.

Source rule: “working name,” “draft,” “to confirm,” and “not started” must stay clearly labeled until an authorized person resolves them.

1. Google reviews (src/data/reviews.ts): all 6 reviews are invented samples. Replace with genuine Google reviews (name, town, stars and text) only after they exist and are approved. The “5.0 · 40+ reviews” badge is invented; use a real rating/count only when available.
2. Google profile link: buttons point to a Google Maps search URL placeholder. Replace with the business’s real “write a review” link from its Google Business Profile, once the correct profile exists.
3. Daniel’s photo (public/t/daniel-founder.jpg): the note says this is a stock photo of a stranger. Replace it with an approved real photo of Daniel before launch.
4. Daniel’s story details: the note says they were written from brief bullet points (doctor dream, grandparents and caregiver years). Have Daniel read and correct every personal detail before launch.
5. Transformation photos (public/t/transform-*.jpg): the note says these are random internet photos, not company work. Replace them with genuine job photos (same angle before/after, natural light) only when available and approved.
6. Unverified business claims: the note specifically flags “background-checked team,” “years as a caregiver,” pricing bands and “40+ reviews.” Confirm each is true and keep supporting proof before launch; otherwise remove it.
7. Footer disclaimer: the note says it was softened for the mockup (“Some images are illustrative”). Restore the strict version or keep only with real photos labeled.

The older mockup notes say that code carries MOCKUP comments at each spot and that nothing there should ship to a production business site as-is. Keep that warning until all facts, assets and permissions are resolved.