Using Involve Resume

Plans, Credits and Limits: What Each Tier Actually Unlocks

What the free tier is, what the six permissions are called, how many AI rewrites and applications each plan holds, and where the counting actually happens.

The pricing question people ask is "what do I get". The more useful question is "what am I allowed to have a machine do for me", because that is what the tiers actually differ on. The documents are the same on every paid tier.

The free tier is the resume editor

Stated plainly, because a price list that advertises something the product then declines is worse than one that never mentioned it.

Free, with no account and no clock:

• The whole job index. Search it, filter it, read it, and see what applying to each listing would involve.
• The resume editor, every design, every country format, the photograph, and downloading the result as a PDF or a Word file.
• Your career profile, and typing your own numbers into your own bullets.

Not free:

• Scoring a resume against a posting, the ranking, the minimum match filter and the breakdown.
• Anything that calls a model. There are zero AI rewrites on the free tier, and there is no free autofill.

Those two were previously listed as small free allowances and were unreachable in practice, because they sat behind a paid button. Printing a number that the product would refuse to honour is the version of this that loses somebody at exactly the moment they were about to use it, so the number is zero and it is said out loud.

Signed in with an unconfirmed email address is stricter still: job listings only, until the confirmation link is opened.

The ladder

Every plan is charged in euro. Prices can be shown in another currency for reading, with the euro price printed beside them, because a converted number on a screen is not what appears on a bank statement.

The six permissions, and why they are six

Internally a plan is a list of permissions rather than a name. There are six, and the names are worth knowing because refusals quote them.

Autofill and auto-apply are separate on purpose, because they are different promises. With autofill, the extension fills one form, or a queue of twenty, and you still press send each time. Auto-apply presses send for you, and you find out afterwards.

Keeping them apart means somebody who paid for forms to be filled can be sure no application was sent for them.

That list lives in one file, and the extension carries a copy of it that is checked byte for byte against the original by the test suite. Two hand-maintained lists eventually disagree, and the day they do, either a paying subscriber is refused or a free one is served, and the person on the wrong end has no way to tell which.

The rewrite allowance

Almost none of this costs money to run. Parsing, scoring, tailoring, the fabrication guard and both file writers execute in your own browser. The one step with a price attached is a call to the writer.

The cold email allowance is separate rather than a share of the rewrites, because the two are different products with different costs. A rewrite is one sentence against a document already in hand. A cold email is a whole message written to a named stranger, and it is the one output somebody could point at a list and run a thousand times.

Most people never feel the rewrite cap. The opener library fixes most weak-opener findings for free, and a whole resume needs one or two presses. The cap is not what a real month looks like; it is what bounds the bill when somebody decides to find out.

The application allowance

Applications are counted separately from rewrites, per day and per calendar month, per kind.

The daily numbers are the ones that bind in practice, and they are set by what a board plausibly tolerates rather than by what the margin allows. Jobs are worked through twenty to forty-five seconds apart, and forty submissions from one address in an hour is the fastest way to get a board to start quietly binning everything from that candidate.

The extension popup prints what is left as two numbers, drawn from the server's own counters and never from anything the browser counted. Where the server could not be reached it says so, because a made-up number there is a promise the run cannot keep and you would find out forty seconds in.

Where the counting happens

Not in your browser. A cap the browser keeps is a cap anyone can lift from the developer console, and these guard the only steps in the product that cost real money per press. The counts live in the database, and the caps in code exist so a screen can print the same number the database will actually enforce. A test parses both and asserts they agree, so a drift is caught by a test run rather than by a complaint.

The application meter is spent at the moment the application is customised, inside that call, and not at submit. So you cannot get a tailored application without being counted, and you cannot be counted and get no document, because the plain drafts are assembled first and kept if the model call fails.

What a refusal says

A refusal that is only a refusal reads as a door closing on the whole product, so each one names the cheapest plan that actually grants the thing rather than the one we would most like sold. Quoting the top tier at somebody refused a three euro feature would be true and useless.

There are five different situations and they need five different sentences: signed out, signed in but unconfirmed, on a plan that does not include it, out of allowance, and allowed with some left. A single message covering all of them is the one where somebody with an unopened confirmation email concludes the product is broken and leaves.

Two honest footnotes

A locked preview never contains the paid text. Where a screen shows you the shape of something you have not paid for, it draws bar widths computed from the length of each produced line. It is not real text behind a blur. A blur over real sentences ships every paid word to every visitor and comes off in two clicks from the developer tools, and presenting that as access control would be worse than charging openly.

There is a comped flag. It is a column on the account that grants everything without payment, it can only be set by an administrative database function and never by anything in a browser, and it exists so the paid flow can be walked end to end during testing without a payment and without a special case in the code.

The ladder is at the plans page. The one thing worth deciding before you look at it is whether you want documents, or whether you want forms filled in.