How to Choose a TripTended Plan for Your Trip Volume

By the TripTended team · First published October 13, 2026

Choose a plan by checking each monthly allowance period against two separate forecasts: new Trips and assistant credits. This guide gives you a worksheet, a worked seasonal example and a way to record what remains unknown before you buy.

Use the pricing page for current amounts and allowances. This exercise evaluates TripTended’s plans; it does not establish whether the product covers every task in your business. For a vendor shortlist, use the separate software pricing comparison.

1. Forecast new Trips by allowance period

Start with the dates of the allowance periods you are evaluating. Check the dates shown in your workspace rather than assuming every period starts on the first of the calendar month. For a purchase you have not made, label the dates as provisional and check the actual period after activation.

Count the Trips you expect to create within each period. A departure date and a Trip creation date can fall in different periods. A Trip already created belongs in your ongoing workload notes, but it is not another planned new Trip simply because you are still working on it.

Copy this table and use at least enough periods to include your expected busy season. Use your own work pipeline or records; do not forecast a peak from an average alone.

For each row, add the uncertain count to the expected count. Then find the largest high-case count across the periods. That is the capacity figure to check first. If you cannot estimate the uncertain count, keep the result open and identify the next evidence you need.

The forecast describes your expected work. It does not reserve capacity or create Trips in the application.

2. Test every period against the plan allowance

The current monthly new-Trip limits are 3 for Starter, 10 for Pro and 30 for Studio. Their monthly assistant-credit allowances are 300, 1,000 and 3,000. Annual subscriptions still have monthly allowances. See current pricing and billing intervals.

For a plan to cover the forecast, every period’s high-case new Trip count must be within that plan’s monthly limit. Do not offset a busy period against unused capacity in a quieter one, or treat twelve monthly allowances as one annual pool.

Illustrative forecast — invented planning inputs, not a customer result:

The expected counts average 5.25 Trips per period. That average hides period B’s high case of 11. Starter fails periods B, C and D. Pro fails B. Studio covers all four high-case counts, for Trip capacity only. Period A’s spare capacity cannot be assumed to cover B.

If the high case were 31 instead, none of these published monthly allowances would cover it. Record the gap and ask the team about available options. Do not assume extra Trips, special allowances or an immediate upgrade outcome that you have not confirmed.

3. Estimate assistant usage independently

Trip count is not an assistant-credit estimate. One Trip might need a small request, several revisions or work completed manually. Requests can consume different amounts, so a fixed credits-per-Trip conversion would conceal that difference.

For representative tasks you have actually evaluated, record the usage shown after completion, the input size and the intended output. Include repeat attempts or revisions when they are part of your workflow. A single small example does not establish the cost of larger tasks. The free-trial guide explains how to keep a limited evaluation focused.

Use a separate usage worksheet for each forecast period:

Sum the budgets for that period. Keep assumptions visibly separate from observed usage. If any necessary task remains unknown, mark the credit check incomplete; entering zero would imply that you have established its cost.

Arithmetic example only: suppose you assign 40 credits to each of 20 requests and set aside another 300 credits for uncertain work. The planning total is 20 × 40 + 300 = 1,100 credits. Those numbers are invented budget inputs, not measured task costs or a recommended reserve. Pro’s 1,000-credit allowance would not cover that estimate even in a period with only four new Trips. Studio’s 3,000 credits would cover the arithmetic estimate, but the forecast still needs testing against your own requests.

Manual work does not consume assistant credits. If you choose to complete some tasks manually, revise the request forecast and note that decision. Do not relabel an assistant request as manual to make the worksheet fit.

4. Compare payment commitments after checking capacity

Current monthly prices are USD 19, 39 and 79 for Starter, Pro and Studio. Annual base totals are USD 180, 384 and 780. The annual monthly equivalents shown on the pricing page are not monthly payments.

If you are evaluating a full year at an unchanged plan, twelve monthly payments total USD 228, 468 or 948. This multiplication compares subscription amounts only. It does not establish taxes, refunds, eligibility, future prices or the terms of a later plan change.

Use a billing interval you can assess with the evidence you have. For a seasonal forecast that only covers four periods, do not infer that the remaining eight will fit or that an annual commitment is preferable. Likewise, do not write a budget that assumes a mid-period switch will provide a particular amount of extra capacity. Check the actual purchase or change terms before relying on that outcome.

5. Record the decision and when to recheck it

Copy this decision record. A plan fits the worksheet only when both resource checks are complete and within the corresponding monthly allowances.

Plan review
Review date and price source: [Date / link]
Periods covered and whether dates are provisional: [Dates / status]
Largest high-case new Trip count: [Count / period]
Largest planned assistant-credit budget: [Credits / period / evidence]
Candidate plan: [Plan / new-Trip limit / credit limit]
Capacity result: [Fits / gap / incomplete]
Credit result: [Fits / gap / incomplete]
Billing interval and full base charge: [Interval / amount / USD]
Unresolved purchase question: [Question / owner / next check]
Recheck trigger: [Forecast change / new usage evidence / actual period dates / changed terms]

For the fictional seasonal example, Studio covers the high-case Trip forecast. If its busiest credit budget were the illustrative 1,100, Studio would also cover that arithmetic budget. The record should still say that the credit input is untested and that the remaining periods and purchase terms need checking. This is a provisional planning result, not a guarantee of future workload coverage.

For that worked example, write capacity: fits; credit check: incomplete; candidate: Studio, provisional. A budget assumption is enough to run the arithmetic, but it is not evidence that your real requests will fit.

Recheck when a new client commitment changes the forecast, representative requests use more credits than expected, or the actual allowance dates differ from your provisional dates. Update the worksheet rather than relying on the first conclusion indefinitely.

When you have a checked forecast, review current pricing, evaluate one task in the trial, or contact the team about an unresolved allowance question. Supplier booking and money movement remain external actions; a software subscription does not complete them for you.

Prepared with AI assistance from TripTended’s confirmed commercial rules. All worked inputs are explicitly fictional. The worksheet runs outside the application and does not change billing, create Trips or promise a fixed request cost.