01
Growth
Find and win the right work.
Funnels, prospecting, sales, campaigns and conversion.
HQ · Agency operating system
An agency that moves
when you ask.
HQ gives your people and your agents the same operating context. Ask from Slack, review the decisions and keep the work moving.
MONDAY · CONCEPT VIEW
Agency pulse
PipelineReviewSample status
Client recordsDemoNot live data
CapacityPendingSource needed
Owner decisionsSample queue
Approve prospecting briefConfirm market and review rules
GROWTHScope localisation requestOutside the sample signed scope
CLIENTFriday delivery reviewNo owner decision in this example
CLEARH
Proposed prospecting runNot yet run
Research up to 300 public companies, apply the agreed fit criteria and prepare evidence for owner review. Do not send outreach.
Limit: 300Approval required
DEMO
Fictional records · no performance claim
Concept UIGrowthDeliveryOperationsOne connected agency
The operating record
The business context
should survive the handoff.
Agencies lose time between specialist tools. A prospect becomes a client, a message becomes a task and a promise becomes delivery work. The context rarely travels with it.
HQ keeps the client, the commercial logic, the work and the agency capacity in one record. That gives people a clearer day and gives agents a safe place to work.
02
Delivery
Turn the promise into work.
Briefs, tickets, checks, commitments and active delivery.
03
Operations
Know what the agency can take on.
Resources, finance, process, sprints and weekly attention.
Product hypotheses
What HQ should make
possible for an agency.
Concept scenarios, not production results
The workflows below describe intended product behaviour using fictional records. HQ has not completed these runs, so this page makes no performance, efficiency or conversion claims.
HYPOTHESIS 01
Prospecting when capacity opens
Ask once. Review the evidence.
M
MatteoExample owner request
I have capacity opening next week. Set up the prospecting funnel for boutique hospitality brands. Research up to 300 candidates and bring me an evidence based shortlist. Do not contact anyone.
H
Proposed response
I will show you the brief, sources and approval rules before any research begins.
01
Confirm the briefMarket, capacity window and qualification rules
02
Research public sourcesThe owner can set a maximum candidate volume
03
Prepare an evidence shortlistNo assumed conversion or success rate
04
Request owner approvalNo outreach is sent automatically
What a pilot must measure
Owner timeMeasure research and review time against the current manual processBASELINE NEEDED
Qualification qualityTrack how many owner approved prospects match the original briefBASELINE NEEDED
Cost per approved prospectInclude data, agent runtime and human review costsBASELINE NEEDED
Commercial outcomeTrack replies, meetings and qualified opportunities separatelyBASELINE NEEDED
No estimate will be presented as evidence until a timed, reproducible run and its manual baseline are documented.HYPOTHESIS 02
Client request in Slack
Prepare a scope decision from the record.
# client_orchid · FICTIONAL MESSAGE
Can we add German localisation to Friday's delivery?
- 01Read the signed scope
- 02Check delivery and capacity
- 03Propose the change for owner review
HYPOTHESIS 03
Owner briefing
Return decisions with their sources.
SALES
Example proposal follow up.
DECIDECLIENT
Example request outside scope.
DECIDEDELIVERY
Example work requiring no intervention.
CLEAR01Today
A product concept and an interactive interface using fictional records.
02Next proof
A timed prospecting pilot with a documented manual baseline.
03Claim only after proof
Time saved, cost, qualification rate and commercial outcomes.
One system of work
From first signal
to finished work.
The agent layer is not another app for the team to check. It works through the same records, rules and approvals as the agency.
01
Build the growth system
Set the market, qualification rules, review points and outreach steps once. HQ carries every prospect through the same process.
Signal to pipeline↗
02
Keep client context intact
Requests, decisions, scope and commitments stay with the client record from the first conversation to the final delivery.
Request to decision↗
03
Run delivery with evidence
Briefs, tickets, checks and ownership stay connected. The team sees what changed and why it matters.
Brief to shipped↗
04
Put agents inside the work
Agents can research, prepare and propose. People approve the decisions that affect a relationship, a budget or a client promise.
Context to action↗
Alibaba Cloud integration path
Enterprise agents underneath.
Agency context on top.
HQ does not need to replace the agent runtime. It can expose agency records and approved actions to agents deployed through Alibaba Cloud Model Studio or AgentRun.
This is the proposed integration architecture for the competition concept. It is not presented as a completed production integration.
01
Ask from workSlack, Teams or HQ
02
HQ supplies context and authorityClients, funnels, delivery, capacity and approvals
03
Agents run on governed infrastructureModel Studio or AgentRun, with tools, skills and observability
04
People approve consequential workOutreach, scope, spend and client commitments
Agents do the preparation.
People keep the relationship.BackgroundPrepared work
1Operating record
Designed for agency trust
Useful autonomy.
Clear authority.
Shared record
People and agents work from the same client, funnel and delivery context.
Checkable output
Every recommendation points back to the records and evidence used.
Explicit authority
Research can run alone. Outreach, scope and financial changes wait for approval.
A guided product story
See one agency
move through HQ.
Six connected moments using fictional data and real product logic.
Enter the product story ↗