A startup-offer card usually looks complete: a logo, a headline value, a category, and a button. The missing information is often the destination type. The same listed amount can point to a provider program page, a partner marketplace, a form, or another catalog. Those destinations do not carry the same evidence weight.
Startup Perk List labels each captured route as a provider route, partner route, application form, or catalog route. The label is an observation about the captured URL, not a promise that the destination will stay that way. Use it to decide what you can treat as first-party evidence and what you still need to confirm.
Quick answer: Open the source and ask what the page can prove. A provider page can state current terms. A partner page can describe a path. A form can show required fields. A catalog page can only help you discover the next click. The provider still decides eligibility and approval.
This note sits between the safe-evaluation workflow and the discovery-to-redemption ledger. For the underlying labels, see the methodology and source policy.
1. Treat the destination as part of the record
Section titled “1. Treat the destination as part of the record”Before you copy a number into a plan, record four facts about the link:
| Field | What to write down | Why it changes the decision |
|---|---|---|
| Source kind | Provider, partner, form, or catalog | Sets the evidence ceiling |
| Host | The hostname you actually landed on | Detects unexpected redirects |
| Page title | Exact title at the date checked | Makes a later review repeatable |
| What it can prove | Terms, path, fields, or discovery only | Prevents treating a listing as an approval |
If the host or title does not match the listing, stop and re-label the record. A card that said “provider route” and now opens a partner form is a different offer, even if the headline value is unchanged.
2. Provider route
Section titled “2. Provider route”A provider route is a page the vendor appears to control: a program page, pricing page, support article, or official FAQ. It is the strongest public source in Startup Perk List’s evidence ladder.
A current provider page can usually confirm:
- the program name as the vendor writes it;
- published eligibility language, if any;
- the official next step (apply, activate, or contact); and
- a link to terms, promotional-credit rules, or an account dashboard.
It cannot confirm that your company is approved, what amount you will receive, or whether the program will still exist next week. The AWS Activate credits page is a useful example: it separates access routes and points to promotional terms, but it does not grant a balance to a reader who has only opened the page.
When the listing is a provider route, your first job is to copy the current wording, not the catalog summary. If the provider page is silent about a condition that matters to you, mark needs confirmation.
3. Partner route
Section titled “3. Partner route”A partner route is a page owned by an accelerator, marketplace, reseller, or another intermediary. It can be a valid way to start. It is not a substitute for the provider’s current terms.
A partner page can usually confirm:
- that a path exists through that partner;
- extra steps such as a referral, cohort, or membership; and
- which information the partner asks you to share.
It cannot confirm the provider’s current amount, region, or approval rule unless it quotes a first-party page and that page still matches. Google’s Cloud Program perks page is explicit that a linked perk is provided at the service provider’s discretion. Treat partner copy the same way: useful for discovery, insufficient as the only source.
If the listing is a partner route, add two URLs to the ledger: the partner page you opened, and the provider page it claims to represent. If you cannot find the provider page, the status is verify, not proceed.
4. Application form
Section titled “4. Application form”A form—Google Form, Typeform, or a vendor intake—can show required fields, file uploads, and the questions a reviewer will ask. That is operationally useful. It is still not a terms page.
A form can usually confirm:
- what the applicant is asked to disclose;
- whether a company domain, deck, or incorporation document is requested; and
- whether the form says a human will review the submission.
It cannot confirm the benefit you will receive after submit. Do not treat a pre-filled “up to” amount on a form intro as an approved balance. Record the form URL, the date opened, and the fields that create setup cost. Then look for the provider terms the form is attached to.
5. Catalog route
Section titled “5. Catalog route”A catalog route points at another index, including the snapshot Startup Perk List was captured from. It can help you find a program. It cannot close a decision.
A catalog page can usually confirm:
- that someone listed the offer on a given date; and
- a suggested next destination.
It cannot confirm current eligibility, value, or availability. If Startup Perk List shows Catalog route, treat the card as a discovery aid and immediately open the next first-party page. If that next page is also a catalog, stop and look for the provider host yourself.
This is why Startup Perk List keeps the snapshot date and source host visible on every offer detail page. The dates tell you when the observation was made. They do not refresh the provider’s decision.
6. A one-pass rubric
Section titled “6. A one-pass rubric”After you open the destination, score it with the same three levels used in the evaluation workflow:
- Proceed to inspect terms: you reached a current provider page and can copy eligibility, route, and expiry language into your ledger.
- Verify: you reached a partner page or form and still need the provider’s terms, or the host does not match the listing.
- Pass for now: you only have another catalog, a broken link, or a page that no longer describes the named program.
Write the reason in one sentence. “Verify because the listing opens a partner form and the provider terms were not linked” is more useful than changing the source-kind label by guesswork.
Evidence, boundary, and last verified
Section titled “Evidence, boundary, and last verified”Evidence. The source-kind labels in this article describe how Startup Perk List classifies a captured URL. The AWS and Google examples are first-party pages used to illustrate what a provider page can and cannot prove. They are not a live inventory of offers. The methodology and source policy explains Observed, Needs confirmation, Historical, and Editorial view.
Boundary. This article is an original Startup Perk List editorial workflow. It does not change a provider or partner decision. Only the current destination and an account-specific confirmation can decide eligibility, amount, or approval. See About this journal for independence and corrections.
Last verified. The linked provider examples and this workflow were checked on 2026-08-30 (Asia/Shanghai). Re-open the destination immediately before sharing company information or applying. A redirect can change the source kind after this note is published.
Final check
Section titled “Final check”Open the listed URL. Write down the host, page title, and source kind you actually see. If the page cannot state current terms, do not copy the headline value into a budget. Find the provider page, or mark the offer needs confirmation and ask one concrete question.