taskix
Describe a job
Sign in Become a provider
Language
Colour theme
The flow

From describing the need to a close backed by proof

Six stages. At every stage it is clear who sees what, where your money sits, and what can no longer be undone.

Try the live demo Read the six stages
01See it work

Do not watch a demo. Use one.

One job across six tabs. Ask Taskix a question, flip the matching gate, place the hold, then try to break a rule. Every reaction below is enforced by the system, not written on a page.

Taskix LiveSample flow
Pick a job
TaskixClarifies your request · a verified pro does the work
Your request at a glanceUpdates as you talk
Category
Symptom
Urgency
Media
Your address
Diagnosis
Price
You said confirmed by youFrom your words read from your messageTo confirm asked, not assumedUnknown left empty, not guessedLocked hidden until acceptanceThe pro decides on site, the person doing the job
  1. Described
  2. Matched
  3. Booked
  4. Proof sent
  5. Closed
Illustrative walkthrough with sample content. No request is created, no provider is contacted and no payment is taken.
02Stage by stage

What happens, who sees what, what cannot be undone

The demo above plays the flow. This is the written version: each stage with the rule that holds it in place.

01 / 06

Describe what you need

Write it, say it out loud, send a photo or a short video. Add a location.

  • You do not have to pick a category; it is derived from what you described and then confirmed with you.
  • If something is unclear, it is not guessed at — you are asked.
  • Uploaded media is scanned for personal data; media containing images of children is placed in permanent quarantine and no setting can open it.
At this stage no provider sees you or your address.
02 / 06

The request is structured

What you described becomes a complete request with category-specific fields.

  • The category's risk rules apply here: some jobs require an extra document, others a pre-flight check.
  • An estimated price range may be shown. It is not an offer and it binds nobody.
  • The AI does not diagnose the cause of the fault; it ranks possibilities and says when it is unsure.
03 / 06

Matching

Eligibility first, ranking second.

  • The eligibility gate: is the document valid, does the service area cover it, are they free at that hour, is the category open, is there enough capacity.
  • A provider that fails the gate does not enter the list — whatever their score.
  • Those that pass are ranked, and you are shown why each one is on the list.
There is no paid top placement. Ranking is decided by eligibility, not by payment.
04 / 06

Booking

A booking is not confirmed until the provider accepts it.

  • The amount is placed on hold; it is not taken from your account.
  • The moment the provider accepts — and only then — the address is shared.
  • If it is not accepted, the hold is released and another provider is suggested.
The address is not visible before acceptance. This is not a setting; it is a boundary of the system.
05 / 06

On site

On the way · Started · Finished — every transition is on the record.

  • State transitions are enforced in the database; the order cannot be skipped and cannot be reversed.
  • If something unexpected comes up (an extra part, extra time) you are asked and your approval is taken.
  • If the connection drops, the record is held on the device and sent with the same key once it returns — no duplicate record is created.
06 / 06

Closing with proof

Without proof, the job does not close.

  • The provider uploads proof of completion.
  • You accept it; without your acceptance nothing is charged.
  • If you dispute it, the job stays open and the process starts.
An attempt to close without proof is rejected at the database level.
03Payment

Where your money sits

This is the most asked question. The answer is one sentence: it does not leave your account until you accept the work.

Every money movement is written into a double-entry ledger, and that ledger cannot be deleted. If there is a mistake the entry is not edited; a reversing entry is opened. That way the history always stays readable.

  1. Booking request

    The amount is calculated; nothing has happened yet.

  2. Hold

    The amount is held on your card; it does not leave your account.

  3. Provider acceptance

    If no acceptance comes, the hold is released.

  4. The job is completed and proof is uploaded

    Without proof the next step does not open.

  5. Your acceptance

    If you do not accept, nothing is charged.

  6. Charge and transfer to the provider

    Both movements are written into the ledger.

See the flow by creating a request

In this environment it runs on sample data; no real booking is created and no payment is taken.

Open the request flow
How it works · Taskix