Read by the ad network · the compliance desk · the partner
Four IB sites for readers who say no.
An IB site gets read three times: by the ad network, by a compliance desk, and by a partner deciding whether to trust you.
These four concepts are design work, not client sites. Each takes a different business — a signal desk, a private consultancy, a copy-trading operator, a sub-IB network. Each builds the site that business would actually need. Risk sits beside the claim. Partner economics show their assumptions. Every relationship is named.
Risk, relationships and assumptions sit next to the claims they qualify, not in a footer nobody is sent to.
Four systems, not one skin
Each concept has its own type, colour logic and layout grammar. They share a way of thinking, not a stylesheet.
Measured, then promised
Between 6 and 19 KB of markup and styles gzipped across the twelve introducing-broker pages, and no request to any other server. The build fails above 20 KB.
Built to hand over
Full source, your own hosting, a content guide. No agency lock-in and no platform to depend on.
The four concepts
Four businesses. Four different sites.
The businesses are invented and every figure on them is illustrative. The build is not — each concept is a production-standard front end. Before any of it goes live, the regulatory wording, registration details, broker relationships and risk warnings need review, specific to the operator and the places it serves.
All four handle disclosure the same way. Past that, each turns on only the modules its business needs. Dual-track navigation earns its place when traders and partners are both real audiences. It is not a default.
Module
01 · Signal desk
02 · Private desk
03 · Copy systems
04 · Partner network
Education and public content
Core
Supporting
Supporting
Partner enablement
Regulatory identity and disclosures
Core
Core
Core
Core
Performance presentation
Selective
No
Core
No
Broker comparison or connection
Connection
Comparison
Connection
Multiple brokers
Partner acquisition track
Optional
Optional
Optional
Core
The reviewer’s read
What a reviewer finds.
The left column describes the pattern these concepts were designed against. It is a characterisation, not a measurement. The right column you can check on this site right now.
Read
The typical site
These systems
Where disclosures sit
In a footer, or on a page nobody is sent to
Beside the claim they qualify, in chrome that travels with it
Performance presentation
Screenshots, best month first
Source-labelled and drawdown-first — or absent by design
Partner economics
A headline percentage
The assumptions and the stressed case, on the same surface
Third-party requests
Tag managers, font CDNs, pixels
Zero — fonts self-hosted, verified at every build
Page weight
Rarely measured
6–19 KB across the introducing-broker pages, measured at every build
Ownership
Locked to an agency or a platform
Full source and a content guide, published on your accounts
Design principles
Compliance is a layout constraint, not a footer.
“The studio has one voice so the templates can each have their own.”
01
Name the relationship.
Say who the operator is, which broker they work with, and who holds the account. Polish should never blur who the parties are.
02
Put risk beside the claim.
A claim about performance, income or access carries its assumptions, method and risk right there. Not in a disclaimer several screens down.
03
Design for the actual audience.
A retail learner, an institutional client, an engineer sizing up the system and a partner weighing a deal each need different proof. One page cannot serve all four.
04
Keep integrations replaceable.
Calendars, comparisons, account links and partner widgets sit in named slots, so the front end never depends on one provider.
05
Publish the downside.
One concept publishes its dissent, one its decline criteria, one its losing days, one its worst case. Same principle, four ways.
The four together
Four voices. One exacting standard.
One publishes its dissent, one its decline criteria, one its losing days, one a calculator that argues back. Each shows the part its category usually hides. It is the same thinking on record at asadi.ai.
Vertical 01 builds sites for people who work with a broker. Vertical 02 builds the broker’s own site — a live-simulated account-opening hero for a fictional CFD/FX/crypto broker, market-hours aware down to the minute.