Sales research
Research organisations without losing the source behind each fact, and keep the record when the conversation moves on.
See the workflowThe workspace
Your work moves. Control stays yours.
GOCUX researches, coordinates tools, manages memory and produces deliverables. It stops at seven consequential action classes for your decision. Every result arrives with evidence.
- 01
Describe the outcome
- 02
GOCUX coordinates the run
- 03
Consequential actions stop
- 04
Delivery arrives with its evidence
The workspace
Seven surfaces, one work order.
Each one is a place work actually happens, not a description of one. Pick a surface to see what it takes in, what it leaves behind, and where it stops.
Conversation
- Takes in
- A question, and the context you name as usable.
- Leaves behind
- An answer you can trace back to what it was given.
- Stops at
- A tool call waits for you when it would change something.
Where it earns its place
Start from the work you need done.
The same surfaces and the same approval boundaries. What changes is the material, the vocabulary and what counts as a good answer.
Financial research
Evidence-led work where the citation matters as much as the figure, and an unresolved question stays visible.
See the workflowDocument review
Questions asked across a document collection and answered from the passage, with the scope of the reading recorded.
See the workflowWork with evidence
Work crosses tools. Control stays in one place.
GOCUX turns a scattered manual process into one reviewable work order without hiding where a claim, decision or result came from.
Before
Scattered work, manual control
- Sources live in different systems.
- Context is copied by hand and drifts.
- Approvals disappear into messages and meetings.
- Results and decisions cannot be reconstructed.
With GOCUX
One coordinated, auditable run
- Every source stays attached to the work.
- Tools and context move under one plan.
- Seven consequential action classes pause for a person.
- Every result keeps its evidence and history.
How the work moves
One work order, from the ask to the evidence.
Every run passes the same four states, and the gate is the third of them. Nothing downstream of it starts until a person has decided.
- queued
Describe the outcome
A goal, the scope it may touch, and what counts as done. GOCUX turns that into one work order and chooses the skills the work needs.
- running
GOCUX coordinates the run
Research, tools and company context move under one plan, and every step lands on the order's record as it happens rather than afterwards.
- awaiting decision
Consequential actions stop
One of seven action classes reaches the gate and the run holds. The refused call is quoted word for word, so what you authorise is the thing that was actually asked for.
- done
Delivery arrives with its evidence
The result, the sources behind it and the decisions that allowed it stay on one record. A rejection is recorded too, and never releases the work.
Explore a work order · illustrated example
Work orderGO-2418Example
Instruction
Prepare the Q3 market update and summarize the risks.
- Scope
- Market changes, competitor movement, opportunities and material risks.
- Output
- Executive brief and evidence table.
Agent progress
- Intake
Goal, scope and acceptance recorded on the order.
- Research
Sources read, then attached to the finding they support.
- Approval gate
A consequential action reached the gate, and the run held.
- Deliver
Released only after the decision that authorised it.
Approval gate
Send the operating brief to 12 recipients outside the company
- Tool
- Email delivery
- Effect
- Reaches people outside the workspace, and cannot be unsent
Approval required
Awaiting decisionApproved · releasedheld 00:02 · pending an operator decision (sample)
Evidence ledger
- order.openedQ3 market update · scope and acceptance recorded
- gate.blockedThe refused call is quoted verbatim, not summarised.
- gate.decisionapprove · actor=operator · scope matched
- delivery.sealed4 entries · hash 9f3c…a1d2
Evidence sealed
A hard pause where it matters.
Seven action classes cannot run without a decision. Each decision covers only the attempt it was granted for, is checked again at execution time, and lands in a continuous audit trail.
- Sending things out
- Pauses — approve, edit safely or reject
- Destroying things
- Blocked until a signed decision arrives
- Exporting data
- Pauses with the files in scope listed
- Scheduling work
- Runs only inside approved cadence and safeguard
- Acting in a live session
- Supervised; consequential steps still pause
- Rewriting its own instructions
- Held for review before the new instruction counts
- Putting another agent to work
- Declared up front, scoped to the same policy
Everything outside these seven classes runs inside the limits you set, without stopping to ask.
What GOCUX does
Researches
Reads the web, data and context with sources attached.
Watches signals
Tracks material change without inventing activity.
Produces outputs
Creates reports, tables, documents and code artifacts.
Manages memory
Keeps approved context versioned and correctable.
Schedules work
Runs only inside an approved cadence and policy.
Coordinates work
Keeps tools, decisions and results on one work order.
Trust
Controls that are on, not on the roadmap.
Every workspace gets the same set. Nothing below describes a certification or an intention — the security page says separately that no attestation is claimed.
Company isolation
Work, memory and credentials remain inside the active company boundary.
Execution-time approval
Seven action classes pause for a person. A decision covers only the attempt it was granted for and is re-checked when the action actually runs.
Credentials as references
Connector credentials are stored as server-side references, never held in the browser. A granted credential does not authorise unattended writing.
A ledger that will not guess
Prompts, decisions, tools and outcomes form a continuous audit trail. The audit page has no sample mode — an invented security record would be worse than none.
A stop that means stop
One control refuses new work and blocks every external effect across the installation, without a restart — attributed, reasoned and lifted only on purpose.
- 3,000 GOCUX credits per billing period
- 500-credit daily cap (UTC) · no overage
- Refills: $29 for 3,000 credits, whenever you choose
- No free trial
Make company work move — without giving up control.
Describe the outcome. GOCUX does the rest inside your rules, and stops where you told it to.