Leaving us is as well-engineered as joining us.

Your data and vendor accounts are already in your name, and the code has a published buy-out price. This page walks through the whole exit, step by step, before you ever need it.

  • 30 days to walk, no penalty
  • ∞ data exports, no cost
  • 2×–2.5× capped, transparent buy-out
How the guarantee works See the buy-out math

The 30-day window

30 days. No questions. No penalty.

Every new monthly plan comes with a 30-day guarantee, counted from the moment you sign the agreement. If anything is off (even just the vibes), you can exit the remaining 11 months of your 12-month contract with no further payment obligation, and keep every file we’ve produced. The guarantee is an exit clause, not a refund: the first month’s plan payment, plus Blueprint and build-fee amounts already earned, are non-refundable because they cover service and labor already provided.

What’s covered

  • Exit from the remaining 11 months of your 12-month plan: cancel within 30 days of signing, no further payment obligation, no penalty, no questions asked
  • All your files, content, and accounts are yours to keep regardless of when you walk
  • Clean handoff of vendor account ownership (Cloudflare, Supabase, BigCommerce, etc.). You keep the keys

What’s separate (non-refundable)

  • The first month’s plan payment is non-refundable; it covers the service month you’ve already received
  • Blueprint and build-fee amounts already earned (every build carries them) are non-refundable; they pay for scoping and build work already performed, stage by stage
  • Add-ons added after the original signing have no separate guarantee window
  • A perpetual license to the source code remains a separate, optional lump-sum purchase

Ending the monthly plan

How to end the monthly plan, step by step.

After the 30-day window closes, ending the monthly plan works on a 30-day written-notice rule instead. Sourced from Section 7.3 of your 12-month Services Agreement.

By you, for any reason

Section 7.3 (a)

  • At least 30 days’ prior written notice. The clock starts when we receive notice, not when you decide.
  • Effective no earlier than the end of the Initial Term. Notice can be served during the Term so that termination lands at month 12 or any later month-end.
  • No refund of fees already paid. Monthly fees paid for the notice window are not refunded.
  • No early-exit penalty. The 12-month commitment is honored by the notice window itself.

Example: a client signs on January 1 with a 12-month Term. They can serve notice as early as December 1 (month 12 minus 30 days) for termination effective December 31. Or they can serve notice mid-Term (say, in September) for termination effective on the next available month-end after both (a) the Initial Term is complete and (b) 30 days have passed.

By you, for cause

Section 7.3 (b)

  • Written notice describing the breach in reasonable detail starts the clock.
  • 30-day cure window. TechTailors gets 30 days from your notice to fix the problem; if it’s cured, the engagement continues.
  • If the breach isn’t cured within those 30 days, you may terminate, including mid-Term.
  • Already-paid fees remain non-refundable per Section 5.10. For-cause termination doesn’t change the refund posture.

For-cause is reserved for genuine, documented breach. Routine disagreements about scope or design preferences are not material breach. If you’re considering this path, reach out first. Nearly every situation resolves through direct conversation before any formal notice is needed.

Run your own dates.

The two dates the contract cares about, applied to your calendar. Same rules as the cards above; nothing here overrides your signed agreement.

Initial Term ends
October 24, 2027
Notice + 30 days
November 24, 2026
Earliest effective exit
October 31, 2027
You pay through
October 31, 2027, then nothing further
Buy-out window closes
January 29, 2028 (Section 7.6)

A notice this early falls inside the 30-day window, which starts when you sign. The guarantee's terms apply instead: an exit, not a refund.

What stays in motion during the 30-day notice window

Notice doesn’t pause service. During the 30 days between serving notice and termination effective date, your website remains hosted, support continues at the applicable SLA, and you retain full access to your data export tools. We use the notice window to walk through every Service Account, document handoff steps, and answer any final questions, not to wind down before you’ve actually left.

How to deliver notice (Section 12.1)

Notice must be in writing. Any of the following count:

  • Email to the address designated for notices on your contract’s cover page (notices to TechTailors go to the email on file for our company; the default for new prospects is the address on the Contact page), deemed given when the email is confirmed.
  • Overnight courier (nationally recognized), deemed given the next business day after sending.
  • Certified or registered mail, return receipt requested, deemed given three days after mailing.
  • Personal delivery, effective immediately upon receipt.

Prefer to talk it through first? Call us at 423‑225‑7535 and we’ll help you get the written notice filed. Either way, we confirm receipt in writing within one business day. If you don’t get a confirmation, follow up, because we want to make sure the clock has actually started.

The handover manifest.

Most agencies talk about ownership in marketing copy. We build it into the architecture. Everything that leaves with you, in four pillars:

Your data: always exportable, always free.

Always yours

Every piece of data we touch on your behalf is available to you at any time, in standard portable formats, at no cost, during the engagement and forever after.

  • CMS content: a full export of your EmDash database (from Cloudflare D1, or a pg_dump on Blogging Pro's PostgreSQL). Every post, every content type, every locale.
  • E-commerce data: BigCommerce account is already in your name. No export needed; you already have it.
  • Search indices: per-locale Typesense collection exports as JSON, schema-included.
  • Analytics: PostHog event export (every event, every property); GA4 already in your Google account.
  • Media: full Cloudinary folder download via the Admin API. Bytes, not URLs.

Your accounts: yours from day one.

Yours from day one

Most of your stack lives in vendor accounts created in your name during onboarding, not ours. We’re added as Admins for the duration of the engagement. When you leave, we just step out.

  • Cloudflare: your account, your DNS, your invoice. We remove ourselves as Admin in ~5 minutes, with no DNS interruption. The running site sits on our account until a buy-out; see the code below.
  • EmDash: already in your Cloudflare account. You get Admin; we disable our user and revoke our API token.
  • BigCommerce: already yours. We rotate API tokens and revoke our access.
  • Cloudinary: your account; we’re a collaborator. Removed at offboarding.
  • Typesense Cloud, PostHog, Crowdin, VWO: account transfer supported by each vendor, or full data export if you prefer to provision elsewhere.

The code: a perpetual license via lump-sum buy-out.

Via buy-out

Under the monthly-plan model, the source code is our property. The same is true under WordPress.com, Wix, Squarespace, or any other subscription web platform. But unlike those platforms, we offer a transparent, capped, one-time way to keep the code: the lump-sum buy-out.

When you exercise the buy-out, we copy our shared code packages and build checks into your repository, so it builds without access to our private registry, and move the running site into your own Cloudflare account. The result: a self-contained Astro project with zero TechTailors runtime dependency, licensed for your business use; the shared packages stay ours, under the same license. You can hand it to any developer, hire in-house, or self-host. We’re no longer a single point of failure.

Without the buy-out, your monthly plan ends and so does your access to the running site. Your data and accounts remain yours; the code does not. See the calculator below for exact pricing.

Your transition: actively supported.

Your final 30 days

Your last 30 days are an active handover.

  • Account-by-account walkthrough: we record a video for each vendor account showing where things live, what to monitor, and how billing now flows directly to you.
  • README + architecture handoff: a complete deployment guide, environment-variable reference, and infrastructure diagram.
  • Final-month support: we’re still on the hook for support during your last paid month. Use it.
  • Forwarding addresses: if you want, we can introduce you to one or two trusted independent developers who’ve worked with us before.

All your files, content, and accounts are yours to keep, regardless of when you walk.

Per-service playbook

The exact handoff for every service.

Expand a service to see what you keep automatically, what TechTailors does at handoff, and what you’d need to provision elsewhere if you don’t continue with the same vendor.

  1. Hosting: Cloudflare

    ~5 minutes for your account · ~1 hour to move the site at buy-out

    You keep
    Your Cloudflare account: your domain's DNS, its security settings, your plan, your analytics history. The running site is the exception: it runs on our Cloudflare account, served on your domain.
    We do at handoff
    Remove ourselves as an Admin member and walk you through the dashboard one final time. With a buy-out, we also redeploy the site into your own Cloudflare account. Without one, the site we serve ends with your plan, or sooner if you point your domain elsewhere first, and we list the two DNS records to change.
    If you switch providers
    After a buy-out the site is a standard Astro project: keep it on Cloudflare or move it to another host that supports Astro, such as Netlify or Vercel. Server code written for Cloudflare Workers, like a form handler, needs porting first. Without a buy-out, your domain, content and data move with you; the code stays with us.
  2. CMS: EmDash

    ~2 hours · Admin handover + database export

    You keep
    EmDash itself, already in your own Cloudflare account: its database (Cloudflare D1, or your Supabase project on Blogging Pro), its media, and every content type, user, locale and post.
    We do at handoff
    Make you Admin if you aren't already, disable our user and revoke our API token. Supply a database export if requested. Bundle all media via the Cloudinary Admin API.
    If you switch providers
    EmDash is open-source (MIT): keep it on Cloudflare, or run it on any Node.js host with SQLite or PostgreSQL. Or take the export to another CMS.
  3. E-Commerce: BigCommerce

    ~30 minutes · Token rotation only

    You keep
    Your BigCommerce account, your full store catalog, customer history, order data, and any custom apps. It was always in your name.
    We do at handoff
    Rotate the API tokens we've been using. Remove TechTailors' user access. Hand you the headless frontend repo.
    If you switch frontends
    BigCommerce's standard Stencil storefront is one click away. Or any headless framework (Next.js, Nuxt) can talk to the same BC backend.
  4. Search: Typesense

    ~2 hours · Cluster transfer or self-host

    You keep
    Your Typesense Cloud cluster: collections, schemas, search analytics, API keys.
    We do at handoff
    Transfer cluster ownership (Typesense Cloud supports this via a support request). Alternatively, full collection export as JSON.
    If you switch providers
    Self-host Typesense (GPLv3) in Docker for free; or move to Algolia, Meilisearch, or any compatible engine using the exported schemas.
  5. Multi-language: Crowdin

    ~1 hour · Project transfer or TMX export

    You keep
    Your translation memory, glossary, and every translated file.
    We do at handoff
    Transfer the Crowdin project to your workspace. Or export everything as TMX (industry-standard).
    If you switch providers
    TMX imports into Lokalise, Phrase, Smartling, Weglot, and most other TMS platforms.
  6. Analytics: PostHog + GA4

    ~1.5 hours · Account transfer + event export

    You keep
    GA4 is already in your Google account. PostHog project transfers to your PostHog Cloud org.
    We do at handoff
    Transfer the PostHog project. Export all events to JSON if you'd rather not continue with PostHog. Provide dashboard configs.
    If you switch providers
    The Zaraz GA4 integration runs at Cloudflare's edge, so it stays with your CF account. Swap PostHog for Mixpanel, Amplitude, Heap, or anything else that accepts event ingestion.
  7. Media: Cloudinary

    ~1 hour · Folder download via Admin API

    You keep
    Your Cloudinary account. It was created in your name at onboarding, so it simply stays yours. (Legacy builds on our shared account get every original byte in their folder bundled and handed over.)
    We do at handoff
    Remove ourselves as a collaborator on your account (or supply the full bundle on a legacy shared build). Either way, no URL breakage if you stay on Cloudinary.
    If you switch providers
    Imgix, Bunny.net, ImageKit, or any image CDN with a similar API. The site uses <picture> with local fallback originals, so the worst-case is the local fallback path resolving.
  8. Domain & DNS

    ~10 minutes · Always yours

    You keep
    Your domain registration and all DNS records. Domains are always registered in your name.
    We do at handoff
    Document the DNS records pointing at any TechTailors infrastructure so you know exactly what changes (if any) you need to make.
    If you switch providers
    Standard DNS propagation rules apply. 24–48 hours globally. We'll time the switch with you.

The buy-out math

The price of keeping the code, computed transparently.

Pick your plan, enter your monthly Website Plan cost, and set how many plan anniversaries you’ve completed. The buy-out is that plan’s projected annual cost (add-on services are excluded from the formula) times a multiplier that starts at 2× on Smart Casual and 2.5× on Professional and Black Tie, then drops by 0.25× at every completed anniversary, down to a floor of 1.25× on Smart Casual and 1.5× on Professional and Black Tie. Rounded down to the nearest $100. Per Section 7.6 of the Agreement, you can exercise it at any time during the Term or within 90 days after it ends; the sale itself closes in a separate written purchase agreement. White Tie buy-outs are priced in the custom agreement. Your contract names these plans Launch, Scale, Enterprise, and Custom. The full picture of what you own, what you license and what transfers after a buy-out is on the ownership policy.

Plan
Annual plan cost$0
Multiplier2.5×
Raw amount$0
Buy-out total $0
Your buy-out price at signing and after each anniversary
Anniversary Multiplier Price

The anniversary price applies while your account is in good standing. Buy-out does not include ongoing support, maintenance, hosting, or updates. You’re welcome to come back later. If you do, we sync your site to our latest standards for free.

FAQ

Direct answers from the FAQ.

Full FAQ at /faqs.

  1. Do I own my website and data?
    You own your data, every day, from day one. Service accounts are created in your name from onboarding. A perpetual license to the source code is available via the lump-sum buy-out described above. This is the same model used by every subscription web platform (WordPress.com, Wix, Squarespace), but with a transparent, capped, one-time buy-out rather than a vague “contact sales.”
  2. How does the lump-sum buy-out work?
    The buy-out converts your monthly-plan license into a perpetual one. The cost is your projected annual Website Tier Plan cost (add-on services excluded) times a multiplier: 2× on Smart Casual and 2.5× on Professional and Black Tie at signing, dropping 0.25× at each completed anniversary while your account is in good standing, to floors of 1.25× and 1.5×. Rounded down to the nearest hundred. White Tie buy-outs are priced in the custom agreement. For example, a Professional-tier client whose page plan runs $12,000/year would pay $30,000 at signing and $18,000 from the fourth anniversary on. Lump-sum purchases do not include ongoing support, maintenance, or updates, but you're welcome to return and subscribe later.
  3. What happens to my data if I leave?
    All your data is fully exportable at no extra cost. Service accounts (blogging, e-commerce, analytics, etc.) are opened in your name at onboarding, so they stay yours when you leave; we just remove our access. Anything that lives in our workspace, like a PostHog analytics project, transfers to your own account. If you'd rather not keep an account, we can cancel it on your behalf. Your trust matters more to us than a contract.
  4. What if I need to leave TechTailors?
    We make it easy. Your service accounts stay in your name, anything of yours we host in our workspace (like an analytics project) transfers to you, the running site moves to your account with a buy-out, all data exports are free, and we document your offboarding plan before you even become a client. You can also purchase perpetual code rights via our lump-sum buy-out: 2× your annual page-plan cost on Smart Casual and 2.5× on Professional and Black Tie at signing, dropping 0.25× at each completed anniversary to floors of 1.25× and 1.5×, rounded down to the nearest hundred. White Tie buy-outs are priced in the custom agreement. If you ever come back, we'll sync your site to our latest standards for free.
  5. What if I want to come back later?
    Welcome home. Returning clients get their site synced to our current architecture standards for free: no new Blueprint, no build fee, no penalty, no awkward email exchanges. We'll pick up where we left off.

Questions before you sign?

This page is here precisely so you’d know how leaving works before joining. If anything’s unclear, let’s talk.

Ready to work with us?

See your exact monthly price, then talk to us when you’re ready.

Price Your Build

30-day guarantee on every new plan: an exit, not a refund.