Hops for professional services

Win the work, staff it, and deliver it.

Hops is collaborative AI for professional services firms. Work with @Hops from the first proposal through staffing and delivery, with the client brief, commitments, and plans in one shared space. Your team reviews the work and decides what reaches clients.
  • Turn past engagements into stronger proposals
  • Check capacity before promising dates
  • Track delivery against the engagement budget

Trusted by teams at

  • Altery
  • Amazon
  • Blue Ink
  • Capgemini
  • Globant
  • Merit America
  • Microsoft
  • Miro
  • Novartis
  • Pathstone
  • Semrush
  • Kustomer
The full cycle

Keep the proposal, staffing, and delivery connected.

The proposal sets the scope. Staffing determines when you can deliver it. Hours and decisions shape what the engagement earns. Your team and @Hops work from the same commitments as the work moves forward. Demos use fictional engagements and illustrative figures.

Start the proposal with work your firm can stand behind.

@Hops drafts the proposal from the client's brief, relevant past engagements, and your firm's format. Review the approach and evidence together, ask for revisions in comments, and keep fees and commitments with the partner.

Check the redlines against your terms and capacity.

Ask @Hops to compare the SOW with your standard terms and bookings, then flag payment changes, liability terms, and start-date conflicts for your review. AI can make mistakes. This is not legal advice or a replacement for human judgment and licensed professionals. Your partners and counsel decide.

Know who can do the work before promising dates.

Ask @Hops to build a staffing view from your bookings tables. Compare skills, relevant experience, and availability by client and week. Spot conflicts, agree on a staged start, and pencil in the team only after the engagement lead approves.

See what the pipeline could mean for the bench.

Bring confirmed bookings, penciled staffing, and likely pursuits into one forecast. Keep committed work separate from probability-weighted demand, compare utilization with your target, and review expected engagement margin using your fee and cost assumptions. Your team checks the inputs and calculations.

Catch the delivery risk before the client checkpoint.

Keep workstreams, milestones, and dependencies beside hours used against the engagement budget. Ask @Hops to flag delays and record risks and decisions from the thread. The lead reviews the impact, assigns owners, and agrees on the recovery plan.

Have the status draft ready for the engagement lead.

Schedule @Hops to draft the weekly client update from the workplan, risk log, and analysis. Bring progress, budget, and decisions needed into one report. The engagement lead checks the facts, corrects the draft, and approves the email before it goes out.

The firm learns

Give the next proposal more than a blank page.

Your team and @Hops work in shared chats, docs, tables, and apps. Reuse relevant proposals, models, and staffing plans your team can access, then adapt them to the new client's scope and data. Review what carries over before it becomes a new commitment.

Ask @Hops in the thread. It answers from what your team already shared.

Your existing tools

Bring your client files into the work.

Connect supported tools for pursuits, email, and client files. Bring bookings and hours from your existing systems through supported connections or uploads. Start with one engagement, without replacing your PSA or resourcing tool.

Pursuits and proposals

Bring client briefs, deadlines, and account context together for the next proposal or follow-up.

Client files and deliverables

Work from existing documents and slides, with revisions ready for the engagement team's review.

Bookings and hours

Build staffing and delivery views from the tables your firm maintains. Review inputs before making commitments.

Client communication

Draft updates from the work and review them before sending through a connected account.

Your team makes the client decisions.

Review client emails before sending

Email sends from a connected account ask for approval by default. Review the draft and decide when it is ready.

Choose who can access each engagement

Organize client work in separate spaces and grant access to the people who need it. @Hops uses the access of the person asking.

Review replies that draw on private sources

If a reply uses information others in the space cannot access, it is held for your review before sharing. You can edit, delete, or approve it.
FAQ

Questions partners ask

Rolling Hops out across the firm? Explore governance and shared context that stays current as people and AI work together. See Hops for enterprise

Hops is a shared workspace where your team works with @Hops in chats, docs, tables, decks, and apps. Prepare proposals together, build staffing views on your bookings data, and review delivery progress in the engagement's space. Your team reviews the output and decides what reaches clients.

No. Start with the bookings, hours, and workplans your firm already maintains. Bring data into Hops through supported connections or file uploads, then ask @Hops to build a planner or delivery view. Start with one engagement and keep your existing systems where they are useful.

They come from your bookings, available hours, and pursuit estimates. Engagement margin forecasts also use your fee and cost assumptions. Keep confirmed bookings separate from penciled staffing and probability-weighted pursuits. @Hops builds the views; your team maintains the inputs and reviews the calculations before making commitments.

@Hops can compare a statement of work with your standard terms, flag changes, and help draft suggested edits for your review. It can also check proposed dates against bookings you provide. AI can make mistakes and does not replace human judgment or licensed professionals. Partners and counsel make the decisions.

Choose who can access each engagement's space. @Hops uses the access of the person asking. Replies drawing on sources others cannot access are held for that person's review before sharing. They can edit, delete, or approve the reply. Review permissions when reusing work across engagements.

Bring your next engagement.

Start with a live pursuit. Build the proposal, check the staffing plan, and carry the agreed scope into delivery with @Hops.