Yasa Hercules gives projects, tasks and teamwork a shared home. You can describe the outcome, divide the work, assign people and follow progress in the view that suits your day. When selected billable work is ready, an optional Midas connection carries it into an invoice draft for review.
The value starts with a clear next step. Instead of leaving an agreement in a message thread, turn it into a task with the context, responsible people and completion criteria together. A small team can then see what is ready, what is blocked and what needs a decision.
What Yasa Hercules brings together
A project groups a description, people, settings and related tasks. Each task can hold its own description, assignees, priority, status and deadline. Subtasks break down larger work, while prerequisites describe the order in which dependent tasks need to finish.
Lists, boards and agenda views offer different ways to inspect that same work. In addition, saved views retain useful filters for your account. Comments and notifications keep discussion close to the task, so the next person can understand a decision without searching through unrelated conversations.
You can use Hercules independently. Midas is an optional connection for billing, and membership of the private Nexus infrastructure panel is not required. Start with the Hercules service introduction, or read our Yasa Ecosystem overview to see how the applications fit together.
Start a project with an outcome people can recognise
First, give the project a clear name and describe the result you want. Add the relevant status, priority and deadline, then check who should have access. Keep the description practical: the work included, important boundaries and the person who can accept the result. For work that still needs a professional, our SkillJobber guide to briefs and proposals explains that earlier step.
For example, a website refresh could cover a new service page, a contact journey and a final review. The project description should identify the intended site and explain what a successful handover looks like. Our website and digital-services guide provides a useful starting point for that brief.
Next, reopen the saved project and check its details. The project settings guide distinguishes basic project fields from customer and billing settings. Changing the project description does not require changing a shared customer record or your personal Account preferences.
Turn the plan into tasks that can be finished
A useful task names an action and explains the expected result. Include enough context for the assignee to begin: the relevant page or file, the decision already made and any review needed. Then select the intended people and set a deadline where the work genuinely needs one.
Use subtasks for smaller pieces of a larger result. If existing work belongs beneath the task, find it by title or task number and confirm the relationship. In contrast, a prerequisite expresses a sequence: one task must finish before another can be completed. Check the direction before linking them.
For the website example, approving the content can be a prerequisite for building the page. A final review can depend on the build. Consequently, an unfinished prerequisite is a reason to inspect the plan, rather than repeatedly trying to complete the blocked task. The subtasks, comments and dependencies guide explains these relationships.
Choose a view that helps you decide what to do next
Use a list when you need task details together, a board when progress is easier to scan by status, and an agenda when scheduled work is the immediate concern. Changing the view changes how you see the tasks. It does not create a separate copy of the project.
Next, narrow the view with the available project, status, search and sort controls. Save a useful combination under a recognisable name. Because saving with an existing view name updates that named view, check the name before confirming. The search and saved-views guide also covers quick commands and keyboard shortcuts.
For a bulk edit, inspect the actual selection before applying the change. A filter may hide work that still exists, and a saved-view link does not grant project membership. Therefore, clear the relevant filters and check the signed-in account before treating an empty view as missing data.
Collaborate in Yasa Hercules without losing the context
Invite collaborators through the appropriate project or task assignment controls, then check the invitation state. The accepted invitation connects the permitted work to the verified identity. However, an invitation sent and an invitation accepted are different stages; confirm the current outcome when someone cannot see the project.
Keep comments specific to the task. Record what changed, the question that needs an answer or the evidence for a review decision. Meanwhile, Inbox brings assignments, comments and other work notifications together. Read and unread controls help you manage attention without changing the underlying task.
The invitations and notifications guide explains delivery states and available retry controls. A Hercules invitation does not grant a Midas workspace or Nexus resources. Shared identity makes movement between services easier, while each service keeps its own permissions.
Use estimates and repeat settings deliberately
Hour estimates help plan capacity and billable work. They express an expectation, rather than proving the time someone actually worked. Therefore, agree what the estimate means before using it in a customer discussion or reviewing billing. The task editor guide makes this distinction explicit.
For recurring work, review the deadline and supported repeat interval together. The current editor offers daily, weekly, monthly and yearly repetition, with an optional end date. Completing an eligible occurrence can create its next pending occurrence; inspect that result before manually creating another task.
For example, a monthly website review can describe the checks and required evidence in one recurring task. However, a repeating task is separate from a recurring invoice in Midas. The deadlines and repeating-tasks guide explains successor tasks, end dates and how to stop repetition.
Move reviewed billable work from Yasa Hercules to Midas
When billing is part of the project, check the connected Midas workspace, customer, currency and hourly rate. Customer defaults and explicit project settings can have different scopes. Also review the numeric rate when changing currency; selecting another currency does not establish that an amount was converted.
The customer and billing-defaults guide explains the configuration. Saving these settings does not issue, send or pay an invoice. A shared customer edit can affect that customer record, so check the business identity and billing details before saving.
Next, select eligible completed billable tasks and open the Midas handoff preview. Review the exact tasks and intended customer, then choose an existing draft or the supported new-invoice option. Finally, inspect the resulting draft in Midas before any separate approval or delivery action. Follow the completed-work handoff guide for the current steps. For the billing-side review, read our Midas invoicing guide.
If the handoff result is uncertain, check the task and invoice draft before repeating it. A draft is a preparation step, not proof that an invoice reached the customer or was paid. This keeps project completion, invoice preparation and financial outcomes understandable as separate events.
Keep project records and infrastructure responsibilities clear
Some projects also have commission entries for eligible recipients. Authorised managers can record an amount, currency and note, with visibility governed by the project. However, saving a commission records that entry; it does not send a payout. The commission guide explains the distinction.
For technical work, the task can identify a staging environment, release criteria and the evidence needed after a change. The hosting operation still belongs to the authorised infrastructure workflow. Our Nexus hosting and access guide explains environment selection and resource permissions.
For instance, a task marked complete should describe the accepted result, rather than merely saying that a deployment was attempted. If an operation times out, establish its actual outcome before retrying. Similarly, preserve the intended text and load the latest record when another editor has changed the task.
Build a manageable first workflow
Begin with one real project, a small set of clear tasks and the people who need them. Choose a useful view, agree completion criteria and try the workflow through review. Then add recurring tasks or the Midas connection where those features serve the work.
Yasa Hercules is currently free to use with no subscription fee, as stated on its public introduction. That describes the current offer, rather than a permanent pricing promise. You can explore the service and its Hercules help guides before choosing how to organise a wider team.
If you want help connecting a website project, collaboration and a practical handover, contact Yasa. Tell us the result you need, who is involved and where the current process becomes difficult. A clear first project gives that conversation a useful starting point.
