Current source · Hosted reading copy. Local machine references are omitted. Planning content does not establish launch readiness.

Simply Tech: full marketing plan

25 October 2026 | Owner review and local website development | Version 3

1. Strategic decision

Simply Tech should become the clear, approachable service brand for devices, connectivity and smart-home systems at home or at work. The proposed promise is Technology made simple. Premium positioning should come from understandable advice, properly scoped work, prepared technicians, respectful access practices and a useful handover. Avoid making premium mean complicated packages, luxury imagery or an unexplained price premium.

The owner has selected the Simply Tech name direction and assigned all Smart Living / Smart Homes services to it. Glean retains Entertainment and its other home/business service categories. Lucent retains websites, apps, advertising and digital marketing. This plan is for one distinct Simply Tech website, with household and business journeys. It is not a page inside Glean, a new Lucent division or a claim that every proposed service is already available.

The marketing priority is to establish trust in a narrowly deliverable service, prove successful visits and then grow through relevant repeat requests and introductions. A broad catalogue without operating capacity would create expensive unqualified enquiries. Build the website around the complete intended category architecture, but publish only confirmed supported tasks, coverage and appointment options. A local review site can show provisional sections clearly; those sections must not become public service promises by accident.

Three decisions shape the plan. First, device repair, connectivity troubleshooting and smart-home projects have different buying triggers and must have separate pages and measurement. Second, household and business work need different qualification and support expectations. Third, consumer paid-search acquisition cannot be assumed available: the platform restriction below materially changes the channel mix. This is a plan for earning qualified demand, not a forecast that demand exists at a particular cost.

Internal business architecture: Home Services is the intended parent business; Glean, Simply Tech and Pitstop Mobile Auto are sibling subsidiaries. This records intended business architecture, not completed legal formation or a new public parent brand or website. Existing brand offers, calls to action and route, section and form identifiers remain unchanged.

2. Evidence, geography and material constraints

The current identity is navy, electric blue and white with lighter blue accents, illustrated on the reviewed van and car concepts. Vehicle images are branding concepts; they do not prove a staffed fleet, repair workspace or equipment capacity. Name choice is not legal or trademark clearance. Prices, dispatch radius, staff, credentials, parts suppliers, supported devices, response times and service terms remain operating inputs to obtain.

South Florida is a proposed pilot context drawn from the portfolio discussion, not an approved Simply Tech territory. Select an initial catchment using technician base, travel time, parking/access, parts logistics and observed appointment density. Do not publish a Miami, Fort Lauderdale or other city page merely because it is commercially attractive. The website's area page must list confirmed service areas only; before confirmation, it should explain that location eligibility is assessed with each request.

A bounded name check found direct category overlap: Simply Tech Repairs advertises mobile device repair in Georgia, while Simply Tech advertises repairs and on-site/remote support in Vancouver, Washington. These observations create search-distinction and clearance questions, not a conclusion about legal rights. Continue the authorized local build with configurable brand/domain values. Before public naming investment, obtain proper name, entity, domain and handle review. Do not borrow those businesses' reviews, claims or assets. [ST-NAME-1; ST-NAME-2]

Paid Google consumer-support gate: Google's current policy disallows third-party consumer technical support, including hardware repair and connectivity help; it lists an exception for support offered exclusively to businesses. Consumer Google Search and paid YouTube execution are therefore excluded from this launch plan. A genuinely exclusive business offer may be evaluated separately with the actual account, destination and policy review; a mixed consumer destination is not presumed eligible. Do not disguise consumer work as business work or use different wording to evade review. Organic search is a separate channel. Google Ads policy [ST-POL-1]

No private ad account, CRM history, search-volume dataset or local booking ledger was inspected. Keyword groups, audience priorities and channel tests below are hypotheses. Competitor pages establish advertised offers, not independently verified quality, availability or economics.

3. Competitive frame and differentiation

These are four reference offers, not four necessarily independent delivery ecosystems: Samsung and uBreakiFix relationships can overlap. No market shares or price comparison have been calculated. Use the three independent competitive reference groups to test the proposition, not to estimate a market size. [ST-COMP-1 to ST-COMP-5]

The recommended differentiation is one understandable plan from symptom to handover. The customer knows what is being assessed, what is included, what requires further approval and what remains unresolved. Document this as actual service behaviour: a short pre-visit scope; a named accountable service contact; a consented access process; a change-approval step; an agreed acceptance test; and a plain-language completion summary. Until these processes exist, describe them as implementation requirements rather than published guarantees.

A second distinction is connected-system thinking with defined limits. A failing video call may involve Wi-Fi, the internet provider, a computer or room coverage. Simply Tech should assess the relevant system instead of selling a replacement device automatically. It must also identify when an ISP, manufacturer, electrician, specialist recovery provider or managed-service provider is the appropriate route. Referral quality can build trust even when the original request is not revenue-producing.

A third distinction is calm, personal communication. Show real explanations and a clean visit process, with no shame about a customer's technical knowledge and no fear-based security language. Demonstrate what successful work looks like: an agreed connection test, a supported phone test or a usable device setup. Avoid promising that every problem can be fixed, that a repair preserves all data, or that a smart home will never fail.

4. Core consumers and purchase triggers

Demographic targeting should support these situations, not substitute for them. Time-constrained households, professionals, seasonal residents and small firms are useful starting hypotheses. Do not assume affluence equals technical difficulty, or age equals inability. Creative should show varied adults and realistic home/work settings rather than treating one demographic as the problem.

Choose two initial demand cohorts that match actual skills; connectivity and a narrow computer-support menu are a reasonable starting hypothesis. Treat hardware phone repair as a separate readiness decision, even if enquiries can be recorded earlier. Business work should be a separate cohort from launch, so a complex office case does not silently consume household capacity or make conversion figures look stronger.

5. Service and first-offer architecture

The site should organize the offer into Device Repairs, Computers, Wi-Fi & Networks and Smart Homes, with Business as a buyer-specific route. Setup & Support is a cross-cutting service category rather than a promise of unlimited assistance. Every category needs a supported-task list and a route for requests outside that list.

Device Repairs: begin with device/model triage. Activate screen, battery or other hardware work only for models, parts and environments that the operator can support. An on-location visit may use a suitably equipped mobile workspace; it does not mean performing every repair on a kitchen table. Bench work, manufacturer service and specialist referral should be explained before custody or payment. Do not label parts genuine or a technician authorized without current evidence.

Computers: offer a bounded assessment, new-device setup, suitable troubleshooting, supported component work and explicitly authorized migration or backup configuration. Ask what success means: starts reliably, connects to a printer, completes a specific task or transfers agreed files. Recovery, board repair, malware incidents and critical business systems require separate qualification. A backup discussion is not a promise against data loss.

Wi-Fi & Networks: distinguish coverage, connection stability, equipment configuration, provider service and device-specific issues. The first offer is an assessment with a written next-step plan; equipment purchase should follow evidence, not be the default sales outcome. Guest networks, mesh setup and printer connections can be offered when supported. Structured cabling and complex commercial networks need their own skill, site and installation review.

Smart Homes: own all Smart Living work under Simply Tech, including relevant connected-home assessment, compatible device setup, network integration and user handover. Begin with the desired outcome and existing system. Separate software/configuration from physical electrical, alarm, structural or security-system work. A device list is not proof that Simply Tech may install every product. Glean retains Entertainment projects; agree the technical sub-scope when a project crosses brands.

Business: offer a scoped assessment or service visit for ordinary endpoints, printers, onboarding and network issues. Identify critical services, regulated data, after-hours expectations and whether an existing IT provider controls access. Do not present ad hoc help as a managed IT contract, emergency response, server administration or guaranteed continuity. Refer unsupported work to an appropriate specialist.

6. Pricing and commercial architecture

Premium value should be visible in preparation, explanation, competence and continuity. Recommended structures are a clearly bounded diagnostic block, a defined setup task, or a specific eligible repair with parts and labour itemized. The operator must set actual amounts after reviewing paid travel, preparation, delivery time, tooling, parts, rework, payment costs and overhead with the finance owner.

Before an appointment, explain whether diagnosis has a separate charge, whether any later credit applies, what a visit includes, when further approval is required, and whether bench handling, parts sourcing or a return visit costs extra. Do not publish a starting price that almost no qualified customer can obtain. Do not copy competitor prices or convert their advertised warranties into Simply Tech commitments.

A later support plan could include a specified number of devices, service hours, remote sessions, onsite allowances and overage rules. Develop it only after observed demand and delivery costs support it. Keep a single visit available; a customer with a broken device should not have to understand a subscription first. Avoid unlimited support, automatic renewal or a bundle-saving claim until its terms and economics are actually approved.

Cross-service value can come from coordinating a network assessment and setup during one suitable visit. State actual included tasks, dependencies and separate prices where applicable. For cross-brand work, identify each provider and quote boundary; no assumed combined billing, automatic enrolment or transferable warranty. Avoid counting the same bundled invoice as full revenue for each brand.

7. Customer journey and conversion design

The first digital choice is the problem, followed by Home or Business. The primary action is Request Tech Help. Enquiry is not a confirmed appointment. Use short progressive qualification: category, general issue, supported device context where known, postal code and contact preference. Do not request passwords, full addresses, serial numbers or private files in the public initial form.

After intake, the operator qualifies geography, task, permissions, urgency, device/parts and delivery method. The customer then receives a scoped assessment or estimate, confirms available timing and authorizes the work. At handover, test the agreed result with the customer and record unresolved dependencies. A follow-up should concern that service before inviting unrelated additional work.

The website should reduce the fear of asking the wrong question. Example support line: “Not sure which service fits? Describe what is happening.” An “Other” category must lead to real triage, not an unsupported promise. Do not expose internal routing or queue labels to consumers. If no suitable service is available, say so plainly and offer an appropriate next step only where one exists.

Proof develops in stages. Before first customers, publish the real scope, process and operator facts that can be substantiated. After delivery, request feedback without filtering for positive sentiment. With explicit permission, develop a case study showing problem, agreed work and outcome without personal screens, addresses, credentials or identifying device details. Case studies should distinguish measured results from customer impressions.

8. Go-to-market sequence

Foundation, days 1-30 after operational readiness work begins: finalize the supported-service matrix, business identity, contact ownership, service area and qualified delivery. Build and test the website in local review mode. Complete the name-clearance work, real asset preparation and intake process. Interview prospective customers or partners only through separately authorized outreach. Build a baseline for enquiries, exclusions and reasons for declining work before spending to amplify volume.

Controlled pilot, days 31-60 when gates are met: open only confirmed service categories and a manageable catchment. Start with owned content, appropriate local-profile presence, opt-in customer introductions and one partner type. Use consistent scopes and record delivery effort, travel, repeat visits and customer outcomes. Evaluate household and business cohorts separately. The calendar describes sequence; it is not authorization to launch on a date regardless of readiness.

Refine and expand, days 61-90 after observed performance: retain the best-qualified route, improve pages with actual questions and test one additional eligible channel or cohort. Do not expand service range, catchment and paid spend simultaneously. The finance owner sets contribution, acquisition-cost and cash limits from real costs. The delivery owner confirms spare qualified capacity. Stop an experiment when it sends unsupported demand, creates unresolved service failures or exceeds its approved cap.

The launch decision should require real proof of a working enquiry-to-handover path. A successful website build, impressions or a busy inbox is not proof. Establish a responsible person and backup for triage, technical delivery and escalation. Marketing should make fewer promises while the service learns; a modest supported menu can still be positioned as premium when it is clear and useful.

9. Organic search and local discovery

Use one useful page for each meaningful intent: device repair eligibility, computer support, Wi-Fi/network help and smart-home services. The Business route should explain commercial qualification, not duplicate household copy with business words substituted. Proposed keyword groups include “phone repair at home,” “computer help at home,” “Wi-Fi troubleshooting,” “smart home setup,” and relevant business-network/support phrases. These are research hypotheses; no volumes or expected rankings are claimed.

Titles and headings should identify the task and brand. Add approved geography only where service coverage is real. Publish informative answers to preparation, diagnosis versus repair, supported models, ISP limitations, access consent and specialist escalation. Write from actual service experience rather than producing many thin city pages. Google's people-first guidance supports useful, reliable content; it is not a ranking guarantee. Search guidance [ST-SEO-1]

For a real eligible business, keep business identity, contact and service-area details accurate across relevant listings. Do not publish an office as a storefront unless customers can actually be served there in accordance with the platform rules. Verify the appropriate business-profile setup before activation. Business Profile guidance [ST-SEO-2]

Implement structured data only with actual supported facts and an appropriate schema. Do not invent an address, ratings, price range or service availability to satisfy a markup template. Validate the implementation and understand that markup does not assure enhanced results. Local business guidance [ST-SEO-3]

10. Social, content and reputation

Build recurring content around recognizable symptoms and the visit experience. Recommended pillars are: explain the problem; prepare for a visit; demonstrate a supported result; make connected systems understandable; and show the people/process behind the work. Use short captioned videos, clear carousels and genuine customer stories. Organic YouTube can house deeper explanations and searchable demonstrations; short clips can introduce the same question on other channels.

Useful topics include Wi-Fi coverage versus provider speed, what information helps qualify a phone repair, setting up a new computer, preparing a smart-home project and what happens when work needs a specialist. Avoid instructions that encourage unqualified electrical work or expose customer accounts. Never show passwords, recovery codes, live customer screens or sensitive network details in creative. Re-record demonstrations with controlled devices and synthetic data.

The tone should be patient and practical: “Here is what we check” and “Here is what happens next.” Avoid “Your network is unsafe” fear hooks, impersonating a manufacturer, or targeting people by a claimed personal failing. Monitor real enquiries and route them to intake; public comments are not a place to collect technical credentials or diagnose sensitive problems.

Ask every eligible customer for honest feedback using a consistent process. Keep service recovery separate from promotional consent. Do not fabricate testimonials, selectively present only favourable review invitations, or offer an undisclosed incentive for praise. Build case-study permission into a separate later request, never as a hidden condition of service.

11. Paid media, audio and streaming

Apply ST-POL-1 before any Google-funded campaign. The plan’s channel exclusion and eligibility gates remain controlling; draft creative in the companion kit is not approved for upload.

Paid social is a conditional test, not confirmed eligibility. Current platform/account/creative/destination review is required; the attempted Meta policy fetch in this research did not return accessible content. Start with a specific, truthful service story and a qualified catchment only after approval. Measure qualified enquiries and delivered outcomes; low-cost clicks can be irrelevant. Do not upload customer audiences or install active tracking without the necessary permissions and configuration.

For radio or streaming audio, use one recognizable problem and one memorable action. Test a serviceable geographic area and comparable time window, with a dedicated landing path or campaign identifier and customer-stated source. Audio may create later brand search; do not force every impression into direct-response ROAS. Confirm actual inventory, production standards and current rate proposals before buying.

Hulu/connected-TV should be a later awareness experiment where geographic reach, frequency, capacity and a learning budget justify it. Disney currently directs advertisers to Disney Campaign Manager for Disney+ and Hulu and provides a Hulu media kit. That confirms a route to investigate, not Simply Tech eligibility, a minimum budget or placement availability. Disney advertising, Hulu media kit [ST-MEDIA-1; ST-MEDIA-2]

Use the same proposed video concept across permitted organic and paid placements, but obtain placement-specific approval and adapt aspect ratio, captions, safe zones and duration. Do not infer paid YouTube eligibility from the ability to publish an organic video. No paid channel goes live from this document.

12. Partnerships, offline visibility and retention

Prioritize relationships that improve qualified appointment density: suitable residential communities, property managers, workplaces, independent equipment retailers and businesses whose customers ask for device/network help. A partner pitch should explain supported services, referral consent, accountability and how exceptions are handled. A logo exchange or an introduction is not a verified partnership. Do not promise partner discounts or commission terms before approval.

The car and van should act as mobile brand recognition, with the large name, Home & Business Technology descriptor, short service list and a tested destination. The current QR artwork is sample-only. For future use, choose a managed campaign destination, readable short fallback address and stationary scan testing on actual production templates. Scans measure engagement, not delivered jobs. A compact car's branding does not establish its suitability for repair equipment or device custody.

After a completed service, retain a concise permissioned record of the issue, agreed work and next relevant step. Offer a follow-up about the resolved task, not automatic cross-selling. Useful triggers include a move, a new device, a change in provider or a separately requested smart-home expansion. Obtain permission for ongoing marketing and make opting out easy. Do not treat an acquired Glean customer as an acquired Simply Tech customer or as consent to receive its promotions.

For a relevant Glean Entertainment project, Simply Tech can receive an expressly permitted technical enquiry. Glean remains the project brand for its retained scope; Simply Tech owns the network/smart-home sub-scope. Lucent referrals are limited to customers asking for hardware or networking, with the reverse route for website/app/marketing requests. Each introduction must name the provider and avoid duplicate revenue credit.

13. Measurement, decision gates and ownership

Use the systems packet as the proposed metric and event contract. Report by household/business, service category, catchment, channel, first-time/returning customer and referral source. A qualified enquiry is contactable and fits a confirmed task/area, not just a form submission. Track enquiry-to-qualified, qualified-to-estimate, estimate-to-accepted and accepted-to-delivered transitions, alongside cancellations, unsupported reasons and avoidable return visits.

Channel ROAS relates attributable net service revenue to advertising spend; it is not profit. Paid acquisition CAC and fully loaded acquisition cost answer different questions. Awareness reach, frequency, completed views, direct traffic and brand-search change remain separate measures. Count each customer and transaction once in consolidated reporting; cross-channel platform totals are not safely additive. Finance owns revenue treatment, cost allocations, target economics and stop/scale ceilings.

Before a pilot, agree the eligible cohort, attribution window, baseline, sample sufficiency, budget cap and review dates. Keep observed results blank until measured. Stop or correct a campaign for unsupported leads, poor service quality, missing follow-up capacity or breached cost limits even when engagement looks strong. Expand only when the service can repeatedly deliver and the finance owner accepts the measured contribution. A strong short-term ROAS should not hide refunds, parts costs or unpaid labour.

The owner approves business scope and commercial commitments. The delivery lead owns capabilities, schedules and actual proof. Marketing owns channel selection, creative and funnel learning within approved limits. The systems owner owns intake, consent and event definitions. Finance owns costs and return thresholds. Claude's website lane owns implementation and independent site verification. These responsibilities should be attached to named people before release; documents do not create staffing.

14. Immediate next actions

Complete the local website and marketing packet using this direction. Resolve the name/category overlap before public identity commitments. Select a qualified operator, supported services and actual service areas. Cost the diagnostic/setup/repair offers and define terms. Validate the enquiry-to-handover process, actual asset rights and monitored contacts. Then choose a bounded pilot and eligible acquisition route with the finance and delivery owners. Public launch, advertising spend and live integrations require their own authorization.

This plan is comprehensive in design scope, not proof of demand, channel approval, profitability or operational readiness. It supplies a coherent starting system that can be tested and refined with real customer and delivery evidence.

Download reading copy (Markdown)