What “good” looks like at the end
- Everyone on the pilot can see the same tasks, assignments, and progress for that project.
- Time is logged on real tasks and reviewed on a rhythm you can repeat.
- Project finance shows profitability (earnings, costs, profit) you can explain, and finance can invoice from the same project record.
- You can compare a few baseline numbers (before Pike) to the same numbers from this project.
Absolutely necessary setup
These steps are the minimum so tasks, time, and money stay tied to one real project. Skipping any of them usually breaks profitability or billing later.People, roles, and access
Invite everyone who will touch the pilot and assign workspace roles that match what they really do. See Getting started for sign-in and role overview.
Customer record
Create the customer you will bill, with real name and details, so the project and invoices stay linked to one account.
Cost profiles for anyone who logs billable time
For each member who will log time on the pilot project, complete the Cost profile on their member profile. Labour cost in the project (and therefore profit on Project finance) is calculated from those hourly cost figures and logged hours, not from guesses at the project level.
One project, linked to that customer
Create the project with the real title, team(s), and customer selected. Add the pilot team under Resources (Project resources) with bill rates aligned to how you price the work (member rate on tasks).
Tasks people actually recognise
Create tasks that match how you run the engagement, assign owners and dates, and use My tasks / project Tasks as the shared execution view (Tasks overview).
Time logging and approval
Decide who logs time (Time entry) and who approves it (Time admin). Without approved time on tasks, billable and cost views lag what really happened.
Before day one (recommended)
- Agree where you’ll ask questions (Slack, Teams, email). If you use Slack, connect the workspace and profiles (Slack).
- Skim Core concepts and Project overview so naming in Pike matches how you talk internally.
Day 1: shape the project
- Refine phases and dates if you use them. Use a project template only if it mirrors real delivery.
- Allocate people to tasks and windows from Resources (Allocation properties, Workspace capacity).
Collaboration
- Task-level collaboration: Task properties, Views.
- Account-level context: Customers (comments, tasks list). Optional: Deals.
Plan vs reality: time
- Project time for time budget, billable split, and planned vs actual.
- Log and Time entry for day-to-day logging; Time admin for approvals.
Money: profitability, billing, and accounting sync
Start from Project finance so you understand earnings, costs (labour + expenses), and profit on this project, including the Billable time vs Revenue booked toggle. Cost profile drives the labour portion of costs for people who log time. Workspace-level money: Finance overview and Finance metrics for trends and unbilled work. Invoices: Creating invoices from the project when you bill. Accounting integrations (optional but high value for finance):- QuickBooks: connect from workspace integrations; sync invoices and related financial data between Pike and QuickBooks.
Operating rhythm (suggested)
| When | Do this |
|---|---|
| Weekly | Project resources + Project time. |
| Weekly | Approve time (Time admin); Finance overview for unbilled hours. |
| Weekly | Project finance: profitability, budget vs actuals. |
| As needed | Edit tasks; Project overview for description and status. |
