For AWS partners · your whole zone, free to read
You cannot enrich an account you never found.
The accounts you already have get scored, enriched and funded. The expensive gap is the ones you never had.
Forgeby forges accounts that were never in your CRM, from official public business registers. The cloud measured from the outside, the funded door named, the dossier shaped for your own seat in Partner Central. Rune drafts the opener. A person sends it.
Ten seconds, no account, no person data. The second route reaches a person, not a calendar wall. Bring the data and security questions.
The quarter, as it actually goes
Thursday, 15:20. Nine days left in the quarter.
Nothing in this section is a product. It is the meeting you have already sat in.
- Your board is the same board it was in January.
- The only new names on it came from a customer who changed jobs.
- The webinar filled with people who are already your customers.
- Your PDM asks what next quarter looks like. You scroll the same list.
- Every consultant who could open a new account is billable until March.
That is not a case study. It is a Thursday.
Nobody in that room is bad at selling. The room has nothing new to sell into.
AWS scores and enriches what you have already put in front of it. It cannot add what was never there. AWS’s own Partner Greenfield page says it “does not supply a list of customer accounts.” AWS will score the list you bring, and refer the occasional inbound hand-raiser. AWS brings what AWS brings, on its own timing. The scaled net-new target list has always been yours to find.
And tier is counted in launched opportunities. On the Services Path that is 3 for Select, 20 for Advanced, 50 for Premier. Both halves start from a list of accounts, and yours ran out in January.
Services Path thresholds as AWS publishes them. The Software Path counts differently. Tier counts launched opportunities from both sides, partner-originated and AWS-originated, at parity.
One spine on this page: the account that was not there. Once it exists, the rest runs on the same rails. The estate is already read, the play is already named, the dossier already shapes itself into the opportunity contract AWS publishes. That is further down. It is not the reason you are here.
The maker · every morning, before you are up
I forge it. You close it.
He reads the market, builds the account and drafts the opener. Then he stops: there is no send button in him.
The shelf is counted every night, 02:00 Stockholm
Good morning.
While you slept I read the shelf again: 1 562 773 companies across 12 European markets, counted 14 August 2026, 226 127 reachable today, 264 620 decision-makers on file. I scored what moved and set aside the accounts worth an hour of a person’s time.
That is every morning here. Name your market below and I will tell you what yours looked like at 02:00.
The stakes
Growth starts with net-new accounts.
Tier, funding and co-sell all compound on accounts nobody has opened yet. Opening them is the slow part.
01 · The count
Every launched opportunity started as an opened account.
So did every funded door that came with it. The counting is the easy part. Opening the account is not.
02 · The arithmetic
One rep, one afternoon, one company.
A market holds tens of thousands. That arithmetic is the whole problem.
03 · The funded door
Funding starts with a named account.
Migrate, modernize, build net-new, resell, expand. Rune names the play an account actually fits, in the vocabulary AWS uses in Partner Central, and then names the door your tier can walk.
04 · The terrain
Europe is a market-by-market job.
Each country publishes its companies its own way, with its own rule for how you may make contact.
The wheel
AWS runs half of this. We forge the other half.
Scoring, funding and co-sell are AWS’s own machinery, free to every partner in Partner Central. The ember half is what no one ships: the account, the dossier, the meeting.
Every write to Partner Central sits behind a human approval, and the submit button belongs to your own seat. Rune prepares; a person decides.
The read · live, right now
Name a company. Watch him read it.
No sign-in, no form. The same read the product runs, answering here. Start with your own firm. Company level only: a role, never a person, until you are inside your own workspace.
The dossier
And here is where that read ends up.
One account, all the way to Partner Central. The company below is invented; the shape is the real one, field for field, as AWS’s own API returns it.
The registry row
Nordwerk Industri AB, Gothenburg. 84 employees from the statutory filing, SNI 25.62, domain proven against the register. Nobody brought this account. It was built.
The estate, measured
Their own site resolves into Azure ranges. A workspace tenant on Microsoft 365. No AWS anywhere. Read from the outside, overnight, never asked and never guessed.
The funded door, named
An estate that runs elsewhere is what a migration door is for. Rune reads AWS’s funding catalogue nightly and names the one that fits this account, in Partner Central’s own language.
The person
A named IT decision-maker with a title that carries the mandate. A person writes to them, from their own inbox. Rune drafts and stops.
The meeting
Consent recorded before anything is captured. The brief writes itself afterwards; the follow-up is drafted, not sent.
The draft, in AWS’s own fields
What the meeting proved, mapped onto the opportunity contract AWS publishes. Below is the object, exactly as it goes to Partner Central.
{
"Origin": "Partner Referral",
"OpportunityType": "Net New Business",
"Customer": {
"Account": {
"CompanyName": "Nordwerk Industri AB",
"Industry": "Manufacturing",
"WebsiteUrl": "https://nordwerk.example",
"Address": { "CountryCode": "SE", "City": "Gothenburg" }
},
"Contacts": [
{ "FirstName": "(named)", "LastName": "(named)",
"BusinessTitle": "Head of IT", "Email": "(held in the workspace)" }
]
},
"Project": {
"Title": "Nordwerk Industri: production data platform",
"CustomerBusinessProblem": "Two plants, one reporting stack, month-end close taking nine days.",
"DeliveryModels": ["Managed Services"],
"SalesActivities": ["Initialized discussions with customer"],
"ExpectedCustomerSpend": [
{ "Amount": "12000", "CurrencyCode": "SEK", "Frequency": "Monthly", "TargetCompany": "AWS" }
]
},
"LifeCycle": {
"Stage": "Qualified",
"ReviewStatus": "Pending Submission",
"NextSteps": "Technical validation session booked."
}
}Fictional company, real contract. Field names and values follow AWS’s published opportunity schema; the enums we do not fill are the ones AWS validates against its own list, and those stay for your team to pick.
Your market · ten seconds, no typing
Name your market.
Tap a country. Tap who you hunt. The numbers answer, counted nightly. Person data never shows before sign-in.
A zone is what you buy, whole. Pick as many as you sell into. DACH, Italy and Iberia are not loaded yet; they open at the same price.
The gate
For AWS Partners. The door checks.
Type your work email and Forgeby greets you with your own record from AWS’s partner directory. That record is also what AWS’s machinery increasingly reads when it decides who gets surfaced. Nothing you type here is stored.
Checked against AWS’s public Partner Solutions Finder. If your firm is an AWS partner and the directory misses it, write to partner@forgeby.com and we open the door.
Where these accounts come from
Forged from public registers. Not scraped, not bought.
An account you have never seen raises one fair question. Where did it come from. Here is the whole answer, before you ask for it.
Every source is named.
Each market’s official public business register, read at the source, under that register’s own terms. What a company publishes about itself to the open internet. What you bring, in your own workspace, not trained on and not resold. Never somebody else’s copy. Full provenance per attribute on request, in writing, under the data processing agreement.
We do not scrape social networks.
And buying a scrape does not launder it. We do not show people in public: public pages carry counts and bands, never a name, an email, a phone number or a title.
Person data lives behind sign-in. Always.
There is one line on this product and it does not move. Before sign-in, counts. After sign-in, inside your own isolated workspace, the work. Sign-up is for AWS partners, with the company domain checked against AWS’s own partner directory before a workspace opens. Workspaces are separated by row-level security in the database itself, so no partner can see another partner’s records.
Rune drafts. A human sends.
Rune is openly an AI and says so on every surface. No mass send, no autopilot, no send button in the product. The message leaves your rep’s own inbox and the relationship stays with your rep. We file nothing into AWS by ourselves either: your team submits, in your own Partner Central seat. Every run is logged and visible to the partner it was done for, and every workspace has a spend cap enforced in code.
EU-resident by design.
Your workspace, your records and the library sit at rest in the EU, in Stockholm. One caveat, stated plainly: some inference runs outside the EU under Standard Contractual Clauses. That covers live web search, which the EU region does not offer, streamed responses, which our EU integration does not yet support, and fallback when the EU route is unavailable. No customer records are stored there. Every processor is named and versioned in the published sub-processor list, and that list is the authoritative one.
How to say no.
Where a market publishes an objection or advertising-protection register, it is applied before a draft exists. One email does the rest: access, correction, objection or erasure, answered in 14 days, half the month the law allows. An erasure is a suppression as well as a delete, so the next load of the register does not quietly bring the record back. privacy@forgeby.com
GDPR-aligned, not ISO certified, and we do not claim certifications we have not earned. The whole posture is written out on the trust and security page. If the data conversation is the one you want first, it is partner@forgeby.com and a person answers.
What we can prove today
We are early. We will not borrow someone else’s logos.
There is no wall of customer names here. We could not honestly put one up yet, and an AWS opportunity is not ours to publish in any case, not without written approval from that partner’s AWS partner development manager. The reason there is exactly one name on this page is the same reason yours would not appear on it uninvited: it takes your written say-so, and for anything touching an opportunity, AWS’s too.
- Forgeby is built and deployed on AWS by Novalo Technologies AB, an AWS Advanced Tier Services Partner. It runs on the machinery it sells: the same funded doors, Partner Central lanes and nightly reads.
- Novalo also run their own Nordics market on it, as a partner rather than as the builder, and they have agreed in writing to be named here. They are the first.
- The live read above is not a mock. It calls the same endpoint the product calls and answers on whatever company you type.
- The opportunity object above is the real contract on an invented company. Field names and values follow AWS’s published opportunity schema, and the submit button is dead by design.
- The figures on this page come from the same nightly count the product reads. When that read is not fresh, the page shows a floor instead of a number it cannot stand behind.
One name, given with permission, is the whole of it. We would rather show you one real one than a wall we borrowed. Judge it the way you would judge a supplier with a single reference. Open your own market, free, and see whether the accounts in it are ones you would have found.
Partner status as listed in AWS’s own Partner Solutions Finder.
