Mapped before movement
Inventory the source, destination, volume, ownership, and failure cases first.
Customer Success Programs
Explore our business growth programs, made to help you grow faster.
HoopAI Migration
Template setupStand up the branded foundation quickly.
Recreate the standard header, footer, typography, and limited form styling from an accessible source website.
Controlled cutover
Sequence redirects, validation, permissions, and launch checks around one plan.
Visible exceptions
Record what moved, what changed, what did not move, and who owns the remainder.
The job behind the service
A template is useful when it becomes a maintainable starting point, not a locked visual sample.
What the engagement covers
A scope people can read before they sign.
Every engagement names the work, owners, limits, timing, and handover so expectations stay visible.
- 01
Existing header and footer recreation
Defined against the agreed operating job and acceptance check.
- 02
Typography and limited form styling
Defined against the agreed operating job and acceptance check.
- 03
Standardized page foundation
Defined against the agreed operating job and acceptance check.
- 04
Issue-reporting path for 60 days
Delivered with the open limits, decisions, and next owner recorded.
How the work moves
Structured enough to trust. Human enough to adapt.
The delivery path stays consistent while the details follow the system, team, and outcome in scope.
- 01
Align the outcome
We name the operating job, owner, boundaries, dependencies, and acceptance checks before delivery starts.
- 02
Map the system
We inspect the data, permissions, workflows, integrations, and team habits that the new setup must support.
- 03
Build and verify
We configure the agreed scope, test the real workflow, and resolve launch blockers against the acceptance plan.
- 04
Handover the work
We train the owners, document the operating path, and make open limits visible before the engagement closes.
A human handover
The people doing the work should leave stronger.
Each principle is built into scoping, working sessions, verification, and the final handover.
HoopAI delivery principle
Clarity
The owner can explain the workflow and its boundaries.
HoopAI delivery principle
Practice
The team works through the real path before handover.
HoopAI delivery principle
Continuity
Open risks, limits, and next actions keep their owners.
“The work is finished when the operator can run it, the system can be checked, and the remaining limits have owners.”
Related HoopAI customer story
Evidence from work already in the field.
This published customer story is related to the service area. It is shown as real HoopAI evidence, not as a promise of identical results.
Read the full story Ebhar
Managing nationwide yacht services with AI assistance
“"Knowledge is reusable, handoffs are clean, and we can iterate weekly without waiting on external teams."”
- 239%
- Lead Volume Increase
- 450%
- Faster Response Time
- 82%
- On‑time Completion
Ebhar transformed how yacht owners request services and receive updates. A single Hoop site captures requests, the AI assistant answers and routes, and operations run with clear workflows, dashboards, and billing. Customers see faster responses and reliable follow‑through.
Open customer storyProject pricing
Template setup
A standardized recreation from an accessible source site. Custom design and development are separate.
Template Setup
$250
Recreate the standard visual foundation from an accessible source site.
- Header, footer, and typography recreation
- Limited form styling
- Usually 1 to 2 weeks with a 60-day issue-reporting window
Prices exclude applicable taxes and third-party costs. The signed scope controls the final deliverables, timing, eligibility, and acceptance criteria.
Before kickoff
Inputs and limits stay visible.
Useful service design shows what each side brings and where a separate scope begins.
Engagement facts
- Format
- Remote standardized setup
- Window
- Usually 1 to 2 weeks
- Issues
- Reportable for 60 days
What we need from you
- A named executive sponsor and day-to-day owner
- Timely access to the systems, data, and people in scope
- Decisions and feedback inside the agreed review windows
- An accessible live or staging source URL
Outside the standard scope
- Third-party license, media, travel, and vendor costs
- Work outside the signed scope or acceptance criteria
- Unlimited revisions, requests, or ongoing implementation
- Redesign, content migration, custom design, custom modules, and Marketplace-theme source customization
Questions before the scope
Clear answers before work begins.
Bring the unusual edge cases into the scoping conversation. The written agreement should carry the answer.
01Is Template Setup a redesign?+
No. It is a standardized recreation of the existing header, footer, typography, and limited form styling. It does not include content migration, custom design, or Marketplace-theme source customization.
02What must be available before work starts?+
HoopAI needs an accessible live or staging URL that shows the source design to be recreated.
03How is the final scope confirmed?+
We confirm the outcome, systems, volume, owners, dependencies, exclusions, timeline, and acceptance checks in writing before delivery begins.
04Can the scope change after kickoff?+
Yes. We document the change, its effect on price and timing, and the revised acceptance check before adding it to the engagement.
05Does the price include third-party costs?+
No. Software subscriptions, paid media, travel, data vendors, and other third-party charges are separate unless the signed scope says otherwise.
Start with the job
Plan the next move with the scope visible.
Bring the job, systems, constraints, and deadline. We will turn them into a bounded scope with a clear path to handover.
Talk to sales
Need help choosing? We will route the job to the right service path.