Half your delivery team
doesn't work for you.
Freelancers, specialist studios, white-label partners, the client's own people. Every tool you've tried makes you choose between paying for their seats and losing sight of their work. Axgenta has a third answer.
Every other tool offers you two bad options
Buy them a guest seat
You pay per contractor, per month, for people who touch three tasks a quarter — and you put an outsider inside the workspace where your internal notes, your other clients and your team's performance data live.
Fall back to email
Free, familiar, and it loses tracking completely. Their work is invisible on your dashboard until someone remembers to ask, which is usually the morning the client asks you.
The third answer
A boundary-respecting sync
Vendor work lands on the same dashboard as internal work, with exactly two channels crossing the boundary. No seat to buy, and nothing of yours goes with it.
Five steps, and none of them is “add a user”
01
Invite by email from the task
On a root task you own, open External assignment and type the address — or just type = followed by the email.
02
They get a link, not a briefing
The invitation email deliberately carries no task description and no internal IDs: only who invited them and a call to action.
03
They work an isolated copy
A branded task page shows title, description, due date and status. They can add it to their own workspace as a copy marked Outside Organization.
04
Status syncs back to you
Status, progress and completion time flow onto your task and appear on your dashboard like any other update. No chasing, no status email.
05
Revoke whenever you like
The link deactivates, new posts are blocked, and the history stays readable. The engagement ends without anything being deleted.
Your side never moves.
Internal notes, attachments, reviewers, approvals and OKR links stay in your workspace. They never browse your tenant; you never browse theirs.
How the boundary is enforced
External assignment is a plan-gated feature, with per-task party limits and a monthly invite allowance. See plans →
Your client sees the plan. Your client does not get an account.
The same logic that handles contractors handles the other side of the engagement. Toggle a public link on a project and any stakeholder can open a read-only view — no sign-in, no licence, no onboarding call. Toggle it off and the URL stops working immediately.
When you want it reviewable
Share internally by named person, by department, or by email address. Every grant appears in one “Shared with” list you can review and revoke. The product treats named grants as the safer default and says so.
When you want it on letterhead
Export to Excel or PDF and choose exactly which columns go out — a lean set for the weekly stakeholder note, the full set for the archive. White-label branding is available on Apex and above.
The fields a client project actually needs are already there
You are not bending an internal-ops tool into shape. Projects carry commercial fields natively, and if your team uses the same set every time, you save it as a reusable template — a “Client project” template that pre-loads client name, budget and contract reference on every new engagement.
There is also a project-level note field worth knowing about: whatever you write in it is appended to the description of every task the project generates. It is where the brand guideline, the NDA constraint, or the client's escalation contact goes once, and reaches everyone who touches the work — including the contractors.
Project fields
- Client name
- Contract reference
- Budget
- Risk level — Low to Critical
- Project type — Client, Internal, R&D, Maintenance
- Location
- Sponsor and reviewers
- In-scope and out-of-scope
When an account lead leaves, the account doesn't leave with them
Agencies churn. The usual result is a handover document written in a rush on someone's last afternoon, covering maybe 40% of what mattered — and a successor who spends a fortnight re-contacting the same vendor and re-litigating a decision that was already made for good reasons nobody wrote down.
Axgenta keeps three separate channels on every task — notes for what was learned and what was rejected, comments for what was agreed and with whom, and history for what happened and when. Nobody maintains them as a separate job, because writing them is the work. The handover meeting becomes thirty minutes of pointing at knowledge rather than three sessions of transferring it.
What Axgenta is not, so you don't find out in week three
This is not a time-and-billing system. There are no timesheets, no billable-rate cards and no invoicing, and we would rather say so now than during your trial. Agencies typically keep their billing tool and use Axgenta for the layer above it: who owns the work, whether it actually landed, and what to tell the client on Friday.
Run one client engagement through it
Fifteen days, full access, up to five seats, no card. Pick a live project, invite one contractor, and share the plan with the client. That is the whole evaluation.