for operations, shared-services and back-office teams

Right team. Right process.On time.

Build the form, required steps, team handoffs and deadlines once. machtask uses them to route every request and show each person what happens next.

  • Request forms
  • Required steps
  • Team handoffs
  • Deadlines
.machtask.app

3–30 characters · no card · 3-month pilot

free 3-month pilot · no card · approved within a day

fig. 1 — a worked example: customer refund

Request
  • Customer
  • Order number
  • Reason
  • Amount
routed
Customer operations4h SLA
  • Validate purchase
  • Check refund policy
  • Manager approval — required over $500
handoff
Finance1d SLA
  • Process refund
  • Record transaction
Done PROCESS v12
fig. 2 — where repeatable work breaksthe process is scattered
  • email templates
  • spreadsheets
  • SOP_v7_FINAL(2).pdf
  • experienced people
  • "ask Priya"
One request that carries the form, steps, handoffs and deadline workers open it and see the current process

fig. 3 — try the product here. raise a request, complete the steps, then edit the process.

your-company.machtask.app

Pick something to request — these are configured by you, not by us.

4

A live demo — click anything. Nothing here is saved.

a working example workspace
fig. 4 — what machtask changesfour practical differences
  • 1

    Workers see the steps while they work

    The form, instructions and required checks appear on the request. Nobody needs to open a separate SOP.

  • 2

    The next team gets the work automatically

    Completing one stage starts the next with its team, deadline and the request information already collected.

  • 3

    New work uses the latest process

    Publish a change once. New requests use it; work already under way stays on the version it started with.

  • 4

    The audit trail is part of the request

    Actions, handoffs, timestamps and the process version are recorded as the work is completed.

fig. 5 — three people, one requestrequester, operator and manager
  • The requester

    anyone in the business — unlimited, free

    Fills in one form and can see the request’s progress without chasing another team.

  • The operator

    the team running the work

    Claims the request, completes the required steps and hands it to the next team.

  • The manager

    owns the process

    Publishes process changes and sees owners, deadlines and queues without asking for a status update.

fig. 6 — a handoff between timezonesthe owner and deadline travel with the work
LONDON09:12 GMT

The process owner updates the expense checks and publishes version 12.

PROCESS v12
same request,
same history
MANILA16:12 PHT

The delivery team opens the next request and sees the version 12 checks.

GUIDED ✓

The next team receives the request with its owner, deadline and earlier activity. New starters follow the same published steps as experienced workers.

fig. 8 — is machtask a fit?where it works best

Built for repeatable work that needs a clear owner, required steps and reliable handoffs — deliberately smaller than an enterprise service platform.

Requirement machtask the enterprise suite*
BudgetStart with a free 3-month pilotUsually an annual platform budget
ImplementationBuild forms and workflows yourselfOften needs specialist implementation
RolloutStart with one processUsually a phased rollout
TrainingInstructions appear in each requestUsually separate product training
Changing a processEdit, review and publishMay need a configured change request

* a broad comparison of typical rollout models, not a claim about every vendor.

BUILT FOR
  • Finance, HR, procurement, claims and customer-onboarding teams
  • Contact centres and shared services with frequent team handoffs
  • Teams working from a shared inbox, spreadsheet or collection of SOPs
  • Organisations that want to start with one repeatable process
NOT FOR
  • Sprint planning and software backlogs
  • Enterprise-wide ITSM programmes
  • A to-do list with extra steps

These teams are better served by a project or task-management tool.

fig. 9 — the rate cardthree-month pilot, then simple plans

Pay for the team running the work — not everyone who needs to participate. Anyone in your business can raise a request; requesters are always unlimited and free.

3-MONTH PILOT · $0
Team

$99/month

10 operators

Unlimited requesters

  • Unlimited workflows
  • Approvals & handoffs
  • Full audit history
  • Your own database
Business MOST TEAMS

$299/month

30 operators

Unlimited requesters

  • Everything in Team
  • SSO / SAML
  • SCIM directory sync
  • Advanced permissions
  • Priority support
Enterprise

Let's talk

Operator count to suit

Unlimited requesters

  • Everything in Business
  • Dedicated infrastructure
  • Custom domain
  • Data residency
  • SLA

Requesters can raise and track requests without a paid seat. Operators are the people who claim and complete work. Every workspace begins with a free three-month pilot; no card is required. Choose a paid plan only if you continue afterward. Prices are in USD.

PILOT PROGRAMME

Put one messy process into machtask. Run it for three months. See if it works.

Refunds. Onboarding. Procurement requests. Site faults. Pick something your team currently runs through email, spreadsheets and SOPs, and run the real process in machtask instead.

Your own workspace. Real work. Three months free.

If it works, keep it. If it doesn't, export your data and walk away.

  • 3 months free
  • No card
  • No lock-in
.machtask.app

3–30 characters · no card · 3-month pilot

workspaces are approved by a human — usually within a day

Run one real process in machtask.

Start with the process your team currently runs through an inbox, spreadsheet or SOP. The three-month pilot is free.

.machtask.app

3–30 characters · no card · 3-month pilot

machtask — forms, steps and handoffs for repeatable work. © 2026 A.C.N. 693 677 191 PTY. LTDFeaturesContactTermsPrivacyMT-001 · rev 13