Tenra wordmarkInfrastructure

Process

Documented steps, clean exit.

Tenra treats every project like a finite system: scope, build, transfer. Each phase captures artifacts in Git so owners can audit what shipped and operate without Tenra in the room.

Explore case studies or request a proof pack.

  1. 01 · Intake

    We collect owners, required disclosures, current domains, and a list of forbidden features. This becomes the baseline brief and change log seed.

  2. 02 · Definition

    Sitemap, CTAs, GBP tasks, and redactions are locked in writing. Variation happens inside the agreed scope, never beyond it.

  3. 03 · Build

    We work in a fresh repo with static output, logged contact flows, optional age/consent gates, and nothing that requires ongoing Tenra operation.

  4. 04 · Review

    You approve previews, DNS plans, and GBP screenshots. All edits reference the change log so no one guesses what moved.

  5. 05 · Handoff

    Repos, domains, DNS instructions, and GBP access move to you. Advice packets and runbooks are delivered so you can manage without Tenra, then we exit.

Advice packets are default support

Instead of retainers, Tenra ships advice packets—plain, procedural guides written for non-technical owners. They explain what to do, what not to touch, and how to escalate without reintroducing dependency. They are static, downloadable, and included for every build.

Baseline packets

  • How to maintain your site
  • How to keep the setup correct
  • What to do if something breaks
  • How to leave the setup intact or hand it off later

Situational packets

  • GBP upkeep and verification continuity
  • Media + video embedding guidelines
  • Operating social platforms without dependence
  • Signals that it is time to outgrow this stack

Optional maintenance is a separate engagement. Advice packets are included even if you do not request additional help.

Build-and-handoff terms

Build-and-handoff
A fixed-scope build delivered with repos, documentation, and transfer of ownership.
Owner custody
The client controls domains, hosting, credentials, and operational access.
Runbook
Short, literal documentation covering upkeep, fixes, and future handoff.

Process FAQ

How long does a typical build take?

Most builds run six to eight weeks depending on scope and approvals. We document every phase so there are no hidden steps.

What do we receive at handoff?

Repos, domains, DNS instructions, and short runbooks for upkeep and break-fix. You can operate without Tenra.

What if the scope changes mid-build?

We lock scope in writing. If needs change, we create a new scope and adjust the plan before proceeding.

Availability + lead time

One build at a time, roughly six releases per year. GBP support covers setup, verification, and an advice packet for ongoing hygiene. Maintenance plans, if offered, are optional and separate. Post-launch questions reference the change log—not open-ended support threads.