Fiive's early access release focuses on how agencies and clients actually work together.

Agency and Client accounts

Fiive supports two account types, designed around how each side of the relationship actually works.

• Agency accounts
  Agencies use the Agency Hub to manage clients, connections, requests, tasks, projects, teams, and work across their entire business.
• Client accounts
  Clients use the Client Portal to collaborate with agencies, submit requests, track work, and stay aligned across all agency relationships.

Each account type has its own dedicated environment, while remaining connected through shared relationships and workspaces when collaboration is enabled.

Clients and connections

Fiive is built around managing agency–client relationships.

Agencies can create clients to manage relationships internally, or connect to clients who already have a Fiive account. Clients can remain private to the agency or be shared by inviting the client to collaborate in Fiive.

If a client already uses Fiive, agencies can connect instantly using a connection code. Clients can also create their own accounts and invite agencies to connect in the same way.

When a connection is established, the Agency Hub and Client Portal are linked through a shared workspace for that relationship.

Connections move through clear states that reflect how the relationship is being managed:

• Internal: Managed privately by the agency
• Invited: An invitation has been sent but not yet accepted
• Connected: Both sides have active accounts and a shared workspace
• Disconnected: The relationship is retained as read-only for reference

This approach allows agencies and clients to manage all relationships in one place, whether collaboration happens internally, with invited clients, or through fully connected workspaces.

Relationship management and workspaces

Each relationship, whether private (internal) or shared (connected), operates within its own workspace. This workspace contains all requests, tasks, projects, files, and relationship context for that agency–client partnership.

Work remains scoped to the relationship it belongs to, while contributing to global views across the organisation.

Global requests and tasks

Fiive provides global views for requests and tasks across all clients and connections.

This allows agencies to manage and triage large volumes of work from a single place, including thousands of requests and tasks across many clients, without needing to jump between individual client views.

Requests and tasks remain fully linked to their respective clients and projects, preserving context while enabling operational oversight.

Requests management

Requests represent incoming work. Requests can be:

• Created by clients through the Client Portal
• Created by agencies on behalf of clients in the Agency Hub

Requests move through the following states:

• New
• In review
• Accepted
• Canceled
• Closed

Requests can remain at the account level or be linked to a project. Accepted requests can be converted into tasks for execution.

Tasks management

Tasks represent actionable work. Tasks can be:

• Created directly by agencies
• Created by converting accepted requests

Tasks move through the following states:

• To do
• In progress
• On hold
• Done

Tasks can exist at the account level or be linked to a project, allowing agencies to manage both ongoing relationship work and project-specific execution.

Projects

Projects provide structure and context for related work. Projects currently support the following states:

• Planned
• Active
• On hold
• Completed
• Canceled

Tasks and requests can be linked to projects to indicate what work belongs where. In early access, projects act as high-level containers or epics rather than fully detailed project management tools.

More advanced project planning, tracking, and progress visibility are planned post-early access.

Visibility and access control

Fiive uses scoped visibility throughout the product.

Agencies and clients see information relevant to them, with clear indicators in the interface such as 'Client visible' or 'Agency managed'.

Agencies control what clients can and cannot see, allowing internal work and notes to remain private while client-facing work stays transparent.

Teams and members

Organisations can invite team members to collaborate in Fiive. Early access supports two roles:

• Owner: Full control over the organisation, including organisation details, member management, and billing
• Member: Full access to client management, requests, tasks, and projects, without access to organisation settings or billing

Additional roles and permissions are planned post-early access.

Authentication

Fiive uses secure, passwordless sign-in via email magic links. This approach avoids passwords while keeping access simple and reliable. Additional authentication options will be introduced later.

Fiive is intentionally scoped for early access. The following constraints are known and actively being worked on.

Email delivery

• Emails are sent from a new domain (fiive.co)
• Some emails may initially appear in spam folders depending on the email provider
• Marking Fiive emails as not spam helps improve delivery over time

Performance and scale

Fiive early access is optimised for small to mid-size agency setups.

• Clients table
  Designed primarily for organisations managing fewer than 100 clients
• Global requests and tasks
  Designed to support thousands of items across many clients. Performance may degrade with very large datasets such as 100+ clients and tens of thousands of items.
• Connection-specific views
  Requests, tasks, and projects are each designed to support up to approximately 1,000 items per connection. Performance may degrade as individual request, task, or project counts approach or exceed this level.
• Teams and members
  Optimised for organisations with up to approximately 100 members

Search, sort, and filtering

• Search is currently limited to item titles and names
• Sorting is limited to a small set of core values
• Advanced filtering is not yet available and is a high-priority next step

Dashboard load time

• The Home dashboard currently takes longer to load than other areas of the product
• This has been identified for optimisation

Roles and permissions

• Early access includes only Owner and Member roles
• More granular roles such as admin-level permissions will be introduced later

Account deletion

• Accounts with live connections or Stripe subscriptions, including cancelled plans, must contact support for deletion due to shared data and billing complexity

Favicons

• Favicons are fetched directly from linked URLs
• Appearance and sizing may vary depending on the source website

Early access is about learning from real usage.

• Report bugs or issues
  Email support@fiive.co with details or screenshots
• Share ideas and requests
  Feedback on what would make Fiive more valuable in day-to-day work is always welcome

Work already underway includes:

• Performance improvements across large datasets
• Faster dashboard loading
• Expanded search, sorting, and filtering
• More granular roles and permissions
• Deeper project functionality and visibility
• Continued refinement based on real-world agency workflows

Thank you for taking part in Fiive early access.