An opportunity is a live application or partnership bid. To see your opportunities, open Fundraising Pipeline → Pipeline in the sidebar. They’re shown on a board, one column per open stage.

Permissions

  • Seeing the Pipeline page needs View pipelines and the opportunities in them, with their contacts (pipeline:read:opportunities). Without it the page shows “No access to opportunities”.
  • Changing anything needs Create, edit, move, close and reopen opportunities and link their contacts, and change pipelines and their stages (pipeline:write:opportunities). Without it the board and table are read-only: you cannot add, drag, edit or select opportunities.
  • Creating an opportunity by qualifying a funnel entry needs pipeline:write:opportunities and pipeline:read:opportunities, and also Create and change funnel entries: edit, move stage, park/unpark, qualify/unqualify, link/unlink contacts, log touchpoints and request next actions (pipeline:write:funnel).
  • Setting a next action needs pipeline:write:opportunities and Create, edit, complete, and delete tasks, and register their external keys (tasks:write:tasks), because a next action is a task.
  • Logging a touchpoint needs pipeline:write:opportunities and Log new touchpoints against contacts (relationships:write:touchpoints), because the touchpoint goes on timelines.
  • Seeing an opportunity’s Timeline needs pipeline:read:opportunities and View touchpoint activity on contacts (relationships:read:touchpoints). Without the second, the timeline is not shown.

Ask an administrator if you are missing one of these.

Add an opportunity

There are two ways in:

  • Qualify a prospect in the funnel. In the qualify dialog, Also create an opportunity in the pipeline is switched on by default. The name defaults to the organisation or person, the ask amount to the indicative value, and every contact on the entry is ticked. Each contact keeps the role it had in the funnel, and you can untick any you do not want (at most 50 can be brought across). A funnel entry becomes one opportunity only.
  • Choose New opportunity on the Pipeline page. Pick the organisation or person, then give it a name. An owner, ask amount and decision date are optional.

New opportunities start in the first open stage. They appear on the board a moment after you create them.

If a save cannot be confirmed (for example, the connection drops), the form keeps what you entered and offers Try again. Trying again sends the same request, so it never creates a duplicate.

Move, close and reopen

Drag a card to another column to move it. Dropping a card back on the column it came from does nothing.

Closed stages, such as Awarded, Declined and Withdrawn, sit in the Closed section beneath the board. Each shows its outcome: Won, Lost or Neutral. To close an opportunity, drop its card on a closed stage and confirm. The outcome is recorded at that moment. Changing the stage’s outcome later does not change opportunities already closed in it.

To reopen an opportunity, choose Show closed opportunities and drag its card back to an open column. Reopening does not ask for confirmation.

You can also do all of this from the opportunity itself: open it and choose Move to stage. Moving to a closed stage this way asks you to confirm too.

Edit and add contacts

Open an opportunity to see its details, its stage, and the contacts involved. Choose Edit to change the name, owner, ask amount or decision date. Under Contacts involved, add a contact and choose their role, change a role, or remove a contact.

An opportunity created from the funnel links back to its funnel entry with Open the funnel entry.

Changes appear a moment after you save them. If you edit an opportunity and move it within a second or two, the later of the two wins.

Use the table

Choose Table to list opportunities. Filter by Mine or Everyone’s, by open or closed, and by stage. Select column headings to sort.

Select opportunities to Reassign owner or Move stage in bulk. Bulk moves go to open stages only: close opportunities one at a time, so each close is confirmed. Opportunities already in the chosen stage are left alone.

Change your stages

The stages, their order and each closed stage’s outcome are set on Fundraising Pipeline → Pipeline settings. Anyone who can view opportunities can see them there; changing them needs pipeline:write:opportunities and account:admin:team. See Pipeline settings.

See what needs attention

The numbers above the board count the whole pipeline:

  • Open — opportunities not in a closed stage.
  • No next action — open opportunities with no open task.
  • Gone cold — open opportunities with no touchpoint for 30 days or more, or none ever.
  • Decision due soon — open opportunities whose decision date is in the next 30 days or has passed.
  • Closed this quarter — opportunities closed since the start of the current calendar quarter (a UTC calendar quarter).

Select a number to show only those opportunities, on the board or in the table. Select it again to show everything. Each open card shows how recently it was touched (a flame inside two weeks, a snowflake after) and its next action, or No next action.

Set a next action

A next action is a real task in Tasks. Open an opportunity and choose Set next action, then say what needs doing, when it is due and who it is for. To set one on several opportunities at once, select them in the table and choose Set next action: each gets its own task.

An opportunity can have one open next action at a time. Complete or cancel it before setting another. The task appears on the opportunity a moment after you create it, and leaves it when the task is completed. Closed opportunities can have next actions too, for example to follow up a grant you won.

If a next action cannot be confirmed, the form keeps what you entered and offers Try again. Trying again sends the same request, so it never creates a second task. When you set next actions on several opportunities, Try again resends only the ones that could not be confirmed. Closing the form instead asks you to confirm first, because setting it again later sends a new request.

To finish a next action without leaving the pipeline, open the opportunity and choose Complete under it. This marks the task complete in Tasks. The action shows Completing… until it leaves the opportunity, which takes a moment. Choose View task to open the task in Tasks instead, for example to cancel it or change it. Complete needs both tasks:read:tasks and tasks:write:tasks (but not pipeline:write:opportunities); View task needs tasks:read:tasks. If the task was already completed, cancelled or deleted in Tasks, nothing is changed and the action clears shortly. If Tasks refuses the change, usually because the task’s assignee has left or one of its links is no longer valid, the drawer says so: choose View task to fix it in Tasks.

Log a touchpoint

Open an opportunity and choose Log touchpoint. Choose what happened, such as Application submitted, Funder query, Site visit or Decision communicated, and when, and add notes of up to 10,000 characters.

The touchpoint always goes on the timeline of the organisation or person the opportunity is with. Under Who was involved, choose which of the opportunity’s contacts it also goes to. Only the contacts you choose get it.

The Timeline in the opportunity shows only the touchpoints logged against this opportunity, newest first. A touchpoint that went to several people appears once. You see it only if you can see everyone it went to, so two colleagues can see different timelines for the same opportunity. This is by design: a touchpoint that went to a contact who no longer exists, or to one you cannot see, is left off your view of the opportunity’s timeline entirely. The organisation’s or person’s own timeline still shows it too, with their other opportunities and their funnel activity. A touchpoint takes a few seconds to appear.

If a touchpoint cannot be confirmed on every timeline, the form keeps what you entered and offers Try again. Trying again sends the same touchpoint, so nobody gets it twice. Closing the form instead asks you to confirm first, because logging it again later can add it twice.