Pricing rework and the redesign

23 Apr 2026 – 16 May 2026by Ola Piętka

+4 added~8 edited−4 deletedacross 8 features· 5 releases

The plan structure was rebuilt into three self-serve tiers — Standard, BYOK, and a Partnership tier opened by invitation. A missed payment now starts a 90-day recovery window before any data is removed, and every screen was redesigned.

Key changes

PricingThree self-serve tiers replaced the old plans: Standard, BYOK for teams bringing their own AI key, and a grant-based Partnership tier.
Scheduled lockA missed or cancelled payment now moves an organisation into a 90-day recovery window, with clear banners, before its data is removed.
RedesignEvery surface was reworked — onboarding, the dashboard, the spec view, the export menus, the sign-in pages, and the emails Specsight sends.
All plansAnalysis quality is now identical across tiers; the only difference is capacity — files, projects, and syncs per month.

Worth knowing

Retired plansThe Free and Pro tiers are gone, along with the free trial, the add-seats upgrade, and the downgrade-to-free path.
Spec viewA feature's scenarios are now grouped by context and then category, instead of a single flat list.

Plans & Billing

+3 added~1 edited−3 deleted

ContextActionOutcome

admin on the billing pageviews the page~~Was: the page shows the current plan, the price, the next renewal date, and the current usage relative to the plan caps~~the page shows the current plan name, its price, and the next billing date

admin on the billing page with a scheduled lock dateviews the pagethe page shows when the organisation will be locked if payment is not restored, with a call-to-action to reactivate

admin on the billing page for a locked organisationviews the pagea locked banner explains the organisation is in the 90-day retention window, with options to reactivate before data is purged

organisation whose plan has lapsedmember tries to open a projectthe member is sent to a locked-organisation page that explains payment has lapsed; no spec data is accessible until the organisation is reactivated

~~admin on the billing page for an organisation on the Pro planchooses Add seats to upgrade the subscriptionthe page redirects to a Stripe portal where the admin adjusts seat count and confirms; the change reflects on the next billing date~~

~~admin on any organisation surface during the free trial windowviews the pagea banner across the top of the dashboard counts down the days left in the free trial and links to the billing page to convert to a paid plan~~

~~admin on the billing page for an organisation on the Pro planchooses Downgrade to Freea confirmation explains which features will lock at the end of the billing period; on confirm, the downgrade is scheduled for the renewal date~~

Onboarding

+1 added~1 edited−1 deleted

ContextActionOutcome

user on the onboarding plan step~~Was: picks the Free or Pro plan and continues~~picks the Standard or BYOK plan and continues~~Was: sent to Stripe checkout to complete the subscription, unless the Free plan was picked — in which case the dashboard opens without a payment step~~sent to Stripe checkout to complete the subscription

new user arriving via a partnership grant linkcompletes the organisation setup steppartnership plan applied automatically; the plan and payment steps are skipped and the dashboard opens

~~user on the onboarding plan step who picks the Free planclicks Continuethe dashboard opens directly without a payment step; the team has full access until they hit the free-tier caps~~

Projects

~1 edited

ContextActionOutcome

admin or developer on the new project page with GitHub connectedpicks a repository, branch, and project name and continues~~Was: project created with the initial analysis queued. If the repository turns out to be larger than the plan allows, the analysis fails later and an error explains the limit.~~project created with the initial analysis queued; the project overview opens and shows analysis progress

Connect an AI Tool

~1 edited

ContextActionOutcome

~~Was: AI tool that has just received an authorisation code, hosted on a public URL~~AI tool that has just received an authorisation codeexchanges the code for access tokensWas: Specsight issues a short-lived access token and a longer-lived refresh token. Tools that bind to a random local port for their redirect URL fall outside the verification rule and have to fall back to connection keys.Specsight issues a short-lived access token and a longer-lived refresh token; the tool can now read the spec

Authentication

~1 edited

ContextActionOutcome

user on the login pageenters a valid email and password~~Was: signed in and taken to the dashboard~~signed in and taken to the dashboard, or to the page they were trying to reach

Feature Tree & Scenarios

~1 edited

ContextActionOutcome

user on the spec pageselects a feature from the tree~~Was: the feature's scenarios appear in the centre pane as a flat list, with category labels alongside each row~~the feature's scenarios appear in the centre pane, grouped first by context and then by category

Digests

~1 edited

ContextActionOutcome

user on the reports page with a completed reportopens the report~~Was: the report opens with a summary up top followed by sections for each feature and the changes within~~the report opens with a Specsight-written summary at the top and structured release-notes sections below

Feedback

~1 edited

ContextActionOutcome

user on the feedback history pageviews the page~~Was: every past submission is listed with its category, status, submission date, and any reply from the Specsight team~~every past submission is listed with its category badge, status pill, submission date, and any reply from the Specsight team