ooligo

Terret (formerly BoostUp)

forecasting revenue-intelligence · forecasting · deal-inspection · conversation-intelligence
AI-NATIVE API
RevOps
7.4 /10

What it is

Terret is the revenue-intelligence and forecasting platform that traded as BoostUp until 2025-09-09. The rename was not cosmetic. The company repositioned from a forecasting point tool into an agent platform, and the product now ships as three named surfaces: Terret Nexus, billed as an answer-to-action engine that diagnoses a revenue problem and then deploys agents against it; Terret Forecast, the machine-learning pipeline forecast that is the direct descendant of what BoostUp sold; and Terret Conversation Intelligence. The launch fleet was named Pipeline Builder, Sales Process Agent, Mutual Action Planner, Machine Forecast and Terret GPT, with Nexus carrying its own coaching, workflow, tracking and integration agents.

boostup.ai now 301-redirects to terret.ai. The application still logs in at app.boostup.ai, which is a fair summary of how far the migration has actually run.

Why it shows up in RevOps stacks

  • Forecasting is still the load-bearing module. Whatever the agent framing, the reason this platform gets shortlisted is the same reason BoostUp did — a forecast built from CRM plus activity data that a manager can defend line by line, rather than a roll-up of rep optimism.
  • It reads the systems already in the stack. Salesforce and HubSpot for the CRM spine, Gong and Chorus for conversation data, Outreach and Apollo for engagement, Gmail and Outlook for activity — assembled into a single revenue graph rather than a set of side-by-side reports.
  • Access where the work happens. Nexus surfaces inside Salesforce and answers questions in Slack, so the deal-inspection motion does not depend on reps adopting another console. That has always been the harder half of this category.
  • Named enterprise references. Terret publishes MongoDB, Cloudflare, Carta, Grafana Labs and Udemy as customers, and names MongoDB, Cloudflare and Mistral as build partners on the platform.

Pricing reality

Terret publishes no price. terret.ai/pricing 301-redirects to the demo request form, so every number below comes from buyers rather than from the vendor.

Vendr’s transaction dataset puts the median contract at $30,420/yr, with the observed band running $23,327 to $80,868. That is the number to plan against. Software directories separately list a per-user module ladder — roughly $30/user/mo for Conversation Intelligence, $50 for the agent tier, $80 for forecasting — but the directories contradict each other, one still reporting the product as quote-only, and Terret confirms none of it. Treat the annual band as the budget line and the per-user figures as unverified.

The practical shape: annual commitment, no monthly path, and the quote moves on seat count and on how many of the three surfaces are in scope.

Best for

RevOps teams at $20-200M ARR B2B SaaS where the buying trigger is forecast defensibility — the CRO cannot explain last quarter’s miss, and the fix is activity-grounded signal rather than a better spreadsheet. It fits best where Salesforce is already clean enough to trust and a conversation-intelligence feed already exists.

Don’t buy it for the agent fleet. The agents launched in September 2025 and the public evidence for them is vendor-published. Buy the forecast, which has years of deployment behind it, and treat the Nexus layer as upside to validate in the pilot.

Versus the alternative

  • vs Clari. Clari remains the enterprise default with the deeper reporting surface and the broader platform around it. Pick Clari when board reporting requires fine-grained slicing of forecast variance, or when the org is large enough that the per-seat gap narrows anyway. Pick Terret when the core forecasting function is the requirement and the budget is binding.
  • vs Aviso. The closest competitor by segment and price. Aviso’s predictive modeling is the stronger half of its product; Terret’s daily deal-inspection workflow is the stronger half of this one. Pick on which of the two your managers will actually open every week.
  • vs Gong Forecast. Gong’s forecasting is a module attached to a conversation-intelligence platform, and it shows. Pick Gong-only when conversation intelligence is the primary spend and forecasting is a bonus; pick Terret when the forecast is the reason for the purchase.
  • vs Salesforce-native reporting plus a pipeline-review prompt pack. Under about 50 reps this is the honest alternative, and it costs the price of the prompts. The platform earns its line item when manual inspection stops scaling.

Watch-outs

  • The rename split the paper trail. Reviews, benchmarks and integration docs are scattered across both names, and some directories still carry BoostUp as a separate live product with different pricing. Guard: search both names during diligence and date every source — anything written before 2025-09-09 describes BoostUp, not the product being sold today.
  • The agent capability claims are vendor-stated. Terret’s launch material claims the fleet automates up to 80% of tactical revenue-team activity. No independent measurement supports that figure. Guard: name two or three specific tasks in the pilot scope, measure hours before and after, and make renewal contingent on that measurement rather than on the headline number.
  • Forecast quality degrades on dirty CRM data. Activity-grounded scoring needs the activity to be captured, and the signal thins out where reps work outside the connected systems. Guard: budget CRM hygiene work before rollout, not after, and check email and calendar capture coverage per team during the pilot.
  • Adoption depends on manager enforcement. Reps whose activity is not logged get scored down, and the platform only becomes the system of record if managers run their reviews inside it. Guard: secure CRO-level sponsorship before signing; a RevOps-only rollout of this category stalls.
  • No MCP server. For a team routing pipeline questions through an assistant, Terret has no Model Context Protocol endpoint, and its LLM story is Claude and ChatGPT access inside Nexus rather than an open connector. Guard: if assistant-side access is a requirement, confirm the API covers the specific reads you need before signing, and re-check at renewal.