Implementation Process

1) Engagement Types

Ghost Revenue works primarily on:

DFY Build + Retainer (default model)

Clients are placed on an ongoing retainer after the build phase.

2) Typical Timelines

Timelines are estimates and assume timely access + client responses.

DFY Build: 14 business days
Full infrastructure rebuild: up to 28 business days
Small fixes / automation sprint: 7 business days

Common reasons timelines extend:

Slow client replies
Access not provided within a reasonable timeframe
Personal issues on our end (you acknowledge delays may occur and Ghost Revenue is not liable for such delays)

3) Communication and Updates

Primary communication methods:

Discord 1:1 channel inside the Ghost Revenue server
Discord DMs, Instagram, Telegram, WhatsApp

Availability: Sunday is fully off.

Update cadence: Daily async updates / Weekly 15-minute check-in call.

Calls (as needed):

Initial consulting / discovery call
Optional onboarding call (if the form is not sufficient)
Kickoff / launch call
Optional weekly 15-minute calls (client choice)

4) Client Dashboard & Status

During implementation, the client will receive:

Updates through the preferred communication method.
Visibility into project phases and progress through a custom client dashboard / OS provided after onboarding.

5) Standard Delivery Phases

Ghost Revenue projects generally follow this pipeline:

1

Consulting / Discovery Call

Alignment on goals, constraints, and feasibility.

2

Client Onboarding

Onboarding form submission, tool/account confirmation, access provisioning.

3

Analysis

Review current infrastructure, flows, bottlenecks, and requirements.

4

Scope Definition

Full scoping of deliverables, tasks, timeline, and dependencies.

5

Build

Implementation of the agreed systems, automations, and infrastructure.

6

QA

Validation against requirements and expected behavior.

7

Edge Case Testing

Stress tests, weird scenarios, permission edge cases, payment/access edge cases where applicable.

8

Launch

Controlled release into production.

9

Handoff

Documentation + walkthrough.

10

Maintenance (Retainer)

Ongoing hosting, improvements, and support.

6) Access Requirements

To deliver work, Ghost Revenue typically requires the following access (as applicable):

Discord: ownership access
Notion: workspace invite as workspace owner
Whop: invite as Owner
Domain provider: login credentials (for DNS and related setup)

How access is shared:

Invite-based admin/owner access where possible
Credential sharing when needed

Account setup:

Clients should preferably have accounts created ahead of time
Ghost Revenue can help set up accounts if needed

7) Scope Control & Change Requests

Scope is documented and tracked in a custom client workspace.

Scope is defined using:

A written scope document
A dedicated Notion page containing scope, tasks, timeline, contracts, call recordings, and project assets (custom per client)

If new requests appear mid-project:

During Build phase: changes are quoted and scoped separately
During Retainer: Ghost Revenue decides whether the request is included; if not included, it will be quoted separately

Revisions: Revisions are allowed, with no fixed number stated in advance, and handled based on practicality and scope alignment.

8) QA, Edge Cases, and Launch

QA standard: A structured testing checklist.

Launch sequence:

Internal test
Fix edge cases / small bugs (if applicable)
Full launch

Definition of “done”:

A deployment is considered complete when everything is tested and functioning as agreed in:

The consulting call
The client’s Notion dashboard
Any written agreements and scope documents

9) Handoff

At handoff, clients receive:

Loom walkthroughs (as applicable)
Notion SOPs and documentation
Admin walkthrough call

Ghost Revenue does not provide formal “training” as a separate service, but documentation and walkthroughs are provided to ensure clarity and operational continuity.

10) Retainer, Support, and Maintenance

All clients move onto a retainer after the build phase.

Retainer structure (single tier) includes:

Bot hosting and maintenance
Tweaks and improvements
Async help and support

Exact inclusions/exclusions are determined at Ghost Revenue’s discretion, depending on the request and scope.

Support response time: Within 24 business hours, Monday to Friday, via agreed support channels.

Access during retainer: Ghost Revenue remains admin/owner where required for ongoing maintenance.

11) Client Responsibilities

To keep delivery fast and clean, the client agrees to:

Reply fast and unblock progress
Provide approvals when needed
Pay third-party tool costs
Provide assets and information requested
Avoid second-guessing every implementation step once scope is agreed

12) Unresponsiveness & Pauses

If the client becomes unresponsive or does not provide required access/assets:

Work is paused
Hosting may be stopped immediately until the client resumes cooperation and obligations are met