Questions

The ones worth answering before you email, including the limits, which are stated rather than glossed.

What if my comp plan is not one of your templates?

The templates are starting points, not a menu. Plans are written in a small language that composes the pieces most plans are actually made of: measures, crediting rules, components, tiered or flat rates, multipliers, draws, clawbacks, caps, SPIFFs and guarantees. Most real plans are a combination of those rather than something structurally new.

Being straight about the limits: the language has been validated against fifteen published industry archetypes, of which twelve compile today. The three that do not involve relative ranking between reps, plan mechanics that depend on a manager approving each payout, and retroactive rate changes applied to already-closed periods. If your plan needs one of those, it is not supported yet and we will say so rather than approximate it.

Send us the plan. You will get an honest answer about whether it is expressible, usually with the YAML attached.

Can I start mid-year?

Yes, and most people do. A plan carries an effective date, and you generate only the periods you intend to run here. Attainment that accrued before you started can be set as an opening figure on the payee, so a year-to-date accelerator does not reset just because the tool changed hands.

What you cannot do is retroactively recalculate months that were paid out of a spreadsheet. Those stay history.

What happens to a period once it is approved?

It is frozen. Approval is a deliberate act behind a checklist and a typed confirmation, and after it the period cannot be edited by anyone, including us.

Corrections are adjustments in a later period. This is the single most important design decision in the product: if a closed period could be edited, then a statement a rep read in March could quietly say something different in June, and nobody would be able to prove what they were originally shown.

How do reps see their statements?

They sign in and see only their own published statements, with the same explain tree an administrator sees, the deal, the credit split, the rate, and the arithmetic.

Statements are not emailed out yet; that is the next thing being built. Today a rep has to sign in to look, which is a real gap for a monthly product and is why it is next.

Does AlgoSplit pay my reps?

No, and it never will. AlgoSplit calculates what is owed and exports it in a format your payroll system accepts, Gusto, Rippling, ADP, Paychex, a journal entry, or plain CSV. Your payroll provider pays people.

This is a deliberate limit. Moving money means money-transmitter licensing whose compliance burden would be larger than the entire product.

What do I have to import, and how?

Closed deals, as CSV, JSON, or an Excel workbook, normally the export your CRM already produces. Column mapping is inferred, then remembered, so the second month is a couple of clicks.

Imports are all-or-nothing. If a row is wrong nothing is imported, and you get your file back with the problems marked in place, so you fix the source rather than hunting for what the tool objected to.

What happens to a deal nobody was credited for?

It is reported, never dropped. A deal no credit rule matched is reported as parked, and a deal that was credited but paid nothing is reported as uncompensated, with the reason, whether that is a plan deliberately not paying on renewals, or a payee who is on no plan at all.

Both are money-shaped holes that would otherwise look like a correct statement, and the approval checklist names the people involved before you can close the period.

What does it cost?

$149 a month for the workspace, flat. There is no per-payee rate, no minimum and no cap, so a team of five and a team of fifty pay the same.

No implementation fee, no annual lock-in, and no seat count to manage, for the reps being paid or for the finance people doing the paying.

How do I get an account?

On the site. Create a workspace, put a card on file, and set up the plan and the people you pay. Nothing is charged today; the first invoice comes at the end of the first month.

Questions before you start, email hello@algosplit.com or use the contact form.

Where is my data, and who else can see it?

On Cloudflare, which is the only subprocessor. Every query in the product is scoped to one workspace by a runtime check that throws rather than returning rows from another, and that check is enforced structurally rather than by code review.

There is no third-party analytics, tag manager, or advertising pixel on any page. The security page describes the controls that exist, and is explicit about the ones that do not.

Something else?

hello@algosplit.com , or look through the plan templates to see whether yours is already there.