Works.Ampverse / Proposal · September 2026

A sales system your
next leader can run.

Turn Ampverse's gaming expertise into a working playbook, AI-assisted sales workflows and a GTM Brain: the shared knowledge base your team uses every day.

60 days

Define the model. Build it in your tools.
Test it with your team.

Philippines, Indonesia and regional sales

One core approach, adapted by product, country and seller. A 30-day onboarding path ready for your next sales hire.

Built in Ampverse's accounts. Owned and maintained by your team.

Works.Ampverse / Architecture

One core. Local knowledge.

04 / Seller

Accounts, live deals, preparation and coaching

03 / Market

Philippines and Indonesia, with regional buyer routes

02 / Product

Influencer · Sponsorships · Community activation
Immersive worlds · Gaming media

01 / Core GTM Brain

Company truth, ideal customers, pricing rules,
sales process, glossary, proof and case studies

Sales knowledge beside HQ

The team uses the Brain through Ampverse's chosen AI tool. Shared folders hold the approved content, with named owners and controlled access.

A clear connection to campaigns

Chris defines how HQ shares campaign evidence and receives qualified briefs. Works connects the sales workflows to the interface he provides.

Thailand contributes experience now. A later rollout adds a country layer when Ampverse is ready.

Works.Ampverse / Weeks 1–2

Extract and define the model.

Capture the expertise

Start with leadership and Philippines sellers and CS. Bring in Indonesia and selected Thailand contributors to adapt the core. Use existing documents, pricing and proposals.

Write the sales process

Define qualification, account mapping, proposal and pricing approvals, and handover to CS. Adapt the approach for brands, game publishers and agencies.

Create the Brain

Set up its home, initial content and review rules. Name the maintainer and confirm who can read, edit and approve each area.

Agree the build

Confirm Pipedrive stages, ownership and handovers with Chris. Record the workflow list, connection requirements, CRM baseline and acceptance tests.

Agree the first-release scope by the end of week two. Build from approved material while the remaining interviews continue.

Works.Ampverse / Weeks 3–5

Build the first seller workflows.

Build the agreed Pipedrive process and first AI workflows. Start with the Philippines, then adapt for Indonesia. Sellers test each workflow as it becomes available.

Onboard and find answers

A 30-day onboarding plan and day-one pack. Sellers retrieve sourced answers from the Brain in the chosen AI tool; unanswered questions go to the maintainer.

Find and prepare accounts

Three executable plays, including gaming-signal sourcing, with effort per play and account research. Sellers approve qualification, CRM updates and every outbound send.

Draft proposals

Use the client brief, product and market context, approved pricing, templates and available campaign evidence. A seller checks every draft before it reaches a client.

Stage complete when the team demonstrates these workflows and the agreed Pipedrive changes in Ampverse's accounts.

Works.Ampverse / Weeks 6–8

Test it on real work. Hand it over.

Run, correct, repeat

Philippines, Indonesia and regional sellers use the plays and workflows on live accounts. Works fixes issues and updates the playbook from what the team learns.

Train the team twice

Initial training during the build, then a second round on live work. Weekly working sessions and office hours support practice through handover.

Keep the Brain current

The maintainer practises updating pricing, product information and market rules. Debriefs, unanswered questions and win/loss notes feed a human-approved update process.

Transfer day-to-day ownership

Ampverse receives the playbook, Brain, workflow instructions, onboarding pack, maintenance runbooks and Chris's prioritised build backlog. The internal owner signs off.

The handover test: your team can run, update and troubleshoot the agreed system without Works in the room.

Works.Ampverse / Acceptance

Done means the team can use it.

Process and onboarding

A new joiner, or a nominated tester, follows the process end to end without coaching. Current sellers validate it. The next hire can use the 30-day plan without a rewrite.

Brain and workflows

The agreed content has a home and a maintainer. The team demonstrates the first workflows, including source checks, approvals and handling missing information.

Three executable plays

Each has a target, trigger, steps, owner, effort estimate and success measure. Sellers test them on real accounts.

Internal build specification

Chris receives a sized, sequenced backlog checked against his roadmap, with dependencies and clear ownership.

Baseline and measures

Record available CRM baselines in the first two weeks and compare at handover. Review onboarding time, content freshness, answer resolution, draft turnaround, win rate, pipeline per rep, signal-sourced pipeline and revenue per rep.

If a measure is missing from the CRM, agree how to capture it and label the gap. Targets are agreed from evidence; revenue gains are not guaranteed.

Works.Ampverse / Build boundary

Works builds the sales layer.

Included in this Embed

GTM process, playbook and governed Brain content.
Agreed Pipedrive configuration and the first assistive workflows.
Light connections to CRM, email and calendar using approved access.
HQ connection through the interface Chris provides.
Testing, training, maintenance and technical handover.

Chris and Ampverse own

HQ, campaign tools, the Pipedrive data foundation, warehouse and runtime infrastructure.
Custom APIs, a Slack or HQ assistant, database migration and deeper automation.
Account provision, permissions and internal engineering.
Hiring, selling and running the process after handover.

If HQ's interface is not ready, use approved campaign exports for the first workflows. Live HQ integration stays in Chris's backlog until ready. Custom engineering is specified, not built by Works.

Works.Ampverse / People and cadence

Protect the time to make it work.

Works delivery team

Nathan Clark leads the engagement, bringing extensive experience in sales, RevOps and sales leadership.

Zachary King supports playbook architecture and provides strategic guidance.

Ampverse working team

Name one internal owner with weekly working time and decision authority. Philippines and Indonesia sales and CS join interviews, training and live testing.

Weekly working sessions, with training and office hours during build and adoption. Works leads delivery; your team tests and approves the work.

What makes 60 days work

Internal owner

Weekly decisions and approvals

Access

Accounts and material ready at kickoff

Seller testing

Working sessions booked from the start

HQ dependency

Use approved exports if needed

Agree Ampverse's time commitments before kickoff. The original interview time caps need to include enough room for testing and approvals.

A working first release in 60 days. Delayed access or approvals may move the handover date; extra scope is agreed separately.

Works.Ampverse / Investment

One engagement. One fee.

AUD25,000

Plus GST if applicable

60-day GTM Embed

Same AUD 25,000 fee. Concentrated delivery across eight working weeks, with final handover by day 60.

Software licences, AI usage, third-party data costs and travel are excluded. Any required costs are agreed before purchase.

Payment

Paid upfront

One invoice for the full engagement fee before kickoff.

Agree before kickoff

Start date, Philippines-first sequencing, the internal owner and team time. Confirm the Pipedrive changes and Works / Chris build boundary in the engagement scope.

Thailand rollout, extra workflows, custom engineering and ongoing support are outside this engagement. Any later work is separately agreed.

Next step: agree the scope and commitments, then sign the engagement and schedule kickoff.

A sales system your next leader can run.