Guide · Check library
Email invitations: what to check before you build them.
“Invite a teammate by email” sounds like a form and an email. The parts that make it slip are the ones nobody lists in planning. Here are the ten questions to answer first, and an example plan that shows what the answers cost.
In short. An invitation feature is usually planned as nine parts: a form, a list of pending invites, an accept page, an API, tokens, the email, a table, permission rules and tests. The work that turns up later comes from questions nobody asked: what happens when the invited person already has an account, whether an invite uses a seat, what stops the form from sending spam, and what the sender sees when the email bounces. Answer them before estimating, and add each answer to the plan as a part, a “Not now” item or an open question.
An example: nine parts planned, three found in review
Our example plan is this feature, “Team invitations”, planned for a two-engineer team. The first draft has nine parts. The review added three more: a rate limit on invite sends, a seat limit check, and a direct join for people who already have an account.
With all twelve parts, each estimated as a best, likely and worst case, the plan comes out at 23.5 developer-days at 50% confidence, 26.6 at 80% and 28.6 at 90%, with a realistic range of 18.3 to 30.1. The three parts found in review are 4.0 of the 26.6 days. Left out of the plan, they would have arrived in the middle of the sprint as a surprise of about that size.
These are one example team’s numbers, not a prediction for yours. The point is the shape: the parts everyone lists are not where the date slips.
Accounts and seats
The first two questions change the accept page and the billing logic, so they are the expensive ones to find late.
- What happens when the invited address already has an account? Signing up again should not be the answer. Decide whether they join directly, and what they see if they are signed in as someone else when they click.
- Does an invitation use a seat, and when: on sending or on accepting? What does the admin see when the workspace is at its seat limit, and can they still invite?
- Which roles may invite, and can someone invite a person into a role higher than their own?
The link
An invite link grants access, so treat it like a password. Links get forwarded and pasted into group chats.
- Does the link expire, work only once, and only for the address it was sent to?
- Can an invitation be revoked or sent again, and does the old link stop working when it is?
- What does the accept page show for each state: valid, expired, revoked, already used?
The email
Anything that emails an address a user typed can be used to send spam from your domain, and one abuse report can hurt delivery for every customer.
- Is sending rate-limited, per person and per workspace, and what does the admin see when the limit is hit?
- How does the sender find out that an email bounced? Without the provider’s bounce events, it fails silently and support hears about it a week later.
- Is the email sent from a queue with retries, so a slow or failing mail provider does not fail the invite request or lose the message?
- Does the email say which workspace the invitation is for, and who sent it? A person invited to three workspaces cannot tell “You’ve been invited” apart.
What to do with the answers
Write each answer into the plan as one of three things. A part, with its own best, likely and worst case, if the answer changes what gets built. A “Not now” item, with a reason, if you are choosing to leave it out. An open question, with an owner, if nobody knows yet.
Do this before estimating. An estimate made before the questions were asked is an estimate of a smaller feature. The full list for every area is in the feature planning checklist, and the way to size each part is in how to break down a feature.
Doing this in SprintProof
SprintProof asks these questions for you. After the AI interview and the first breakdown, the “Did you think of…?” gap review matches the plan against a library of 153 checks and asks only the ones that apply, each with why it matters and a suggested part with its own range. You add it as a part or mark it not needed; nothing in the plan changes without a click.
Open the example plan to see the result, or try the range on your own parts in the free estimator.
Plan the feature, not just the document.
Describe the feature and SprintProof interviews you, drafts the breakdown, asks the questions reviewers ask, and gives an estimate as a range with 50, 80 and 90% dates.