Types of Engagements on Storetasker
Storetasker supports three primary types of engagements for Experts: Projects, Repeat (Retainers), and Bills. Each has specific use cases, payment flows, and protections.
1. Project
Definition:
A Project is a one-off engagement where the client accepts your quote and pays in full upfront. The payment is held in escrow until the project is completed.
Payment Flow:
-
Client accepts your quote and pays in full.
-
Funds are held in escrow.
-
Once you mark the project complete and the client approves, your portion of the funds is released to your wallet.
Key Points:
-
Provides maximum payment security.
-
Recommended for most one-off projects.
-
Ideal for new clients or larger scope work.
Use Cases:
-
Small or medium website updates.
-
Single-project design or development tasks.
-
Any work where upfront assurance of payment is important.
2. Repeat (Retainer)
Definition:
A Repeat engagement is an ongoing subscription or retainer arrangement. Payments continue until either the client or you cancel the retainer.
Payment Flow:
-
Payments are billed weekly or monthly on the agreed schedule.
-
Funds are released to your wallet immediately upon receipt, not held in escrow.
Key Points:
-
Designed for recurring or ongoing work.
-
Provides predictable, ongoing revenue.
-
No end date unless canceled by either party.
Use Cases:
-
Ongoing website maintenance or SEO support.
-
Recurring marketing campaigns or content updates.
-
Any service requiring continuous weekly or monthly attention.
3. Bill
Definition:
A Bill is a one-time invoice for work that has already been completed. Bills are not pre-paid and do not offer the same protections as Projects.
Payment Flow:
-
Send a Bill after completing the work.
-
Client must manually approve and pay the Bill.
-
There is no escrow or automated approval.
Key Points:
-
Only use for work already completed and delivered.
-
Does not provide payment assurance—payment relies entirely on client approval.
-
Use cases are limited; Projects or Repeat retainers are generally safer.
Use Cases:
-
Small add-on tasks outside of a previously accepted project.
-
Paid consultations or short-term services where no upfront quote exists.
-
Hourly work that was agreed upon verbally before starting.
Summary:
| Engagement Type | Payment Flow | Protection | Recommended Use |
|---|---|---|---|
| Project | Escrow, paid after client approval | High | Most one-off projects |
| Repeat | Recurring, paid immediately | Moderate | Ongoing/retainer work |
| Bill | Paid after work, client must approve | Low | Limited, post-completion work |
Pro Tip: Use Projects whenever possible for maximum security. Use Repeat for ongoing work, and only use Bills for post-completion invoicing when Projects or Repeat arrangements are not in place.
Help Center