Partners

Partner story TinyFish

From one URL to a campaign-ready brand

How we use TinyFish to make onboarding faster, easier, and more useful from the first conversation.

By Yulong6 min readWith TinyFish

HellyeahTinyFish

Article

What we built: the 10-minute campaign

AIMA, our AI marketing agent, takes a business from signup to a launched advertising campaign in about 10 minutes. The same journey used to take days or weeks: account setup, brand intake forms, creative production, launch, with a waiting handoff between each step.

We reach that speed by moving the important work into onboarding. Before AIMA can create a useful campaign, it needs to understand the business, and with TinyFish, that work starts with a single website URL. TinyFish helps AIMA understand the business behind the URL, so customers spend their time improving the campaign instead of repeating information they already published.

BeforeDays to weeksAccount setupBrand intakeCreativeLaunchwaitwaitwaitWith AIMAAbout 10 minutesOne URLresearchdraft profilereviewCampaign live
Fig 1 The old handoff chain against the AIMA flow. The work moves into onboarding, so the campaign goes live in one sitting instead of across a queue of waits.

Why the first campaign used to take days

A new advertiser brings a goal and a budget. But launching a campaign also requires the offer, the audience, the positioning, the brand voice, the visual system, and the pages an ad should send people to. Most companies have already published all of that, spread across their website.

The traditional flow makes the customer repeat it anyway. A strategist reads the site and sends follow-up questions. A designer asks for logos and colours. An operator checks the offer and landing page. Same context, explained three times, with the days disappearing into the handoffs.

AIMA collapses this into one conversation, and TinyFish runs the research pass before the customer even starts reviewing. The session opens with a draft of the business already on screen.

Told again each timeSame context, three timesCustomerStrategistDesignerOperatorasks againasks againasks againWritten onceOne approved profileCustomerBrand ProfileStrategy reads itCreative reads itLaunch review reads it
Fig 2 Told again each time, against written once. One approved Brand Profile becomes the record every later stage reads from.

Why TinyFish

Every customer website behaves differently. One company explains itself across four plain pages. Another hides the offer behind tabs, filters, or a product configurator. Often the page that matters most isn’t the homepage.

That variety is why we didn’t want to build and maintain our own web integration for each customer: crawlers break, dynamic sites need real browsers, and none of that is our product. Onboarding needs three things from a website: finding the pages that explain the business, reading them as clean content rather than page furniture, and clicking through sites that only reveal their context in a running browser.

We looked at a few web data providers, and TinyFish was the only stack that covered discovery, clean extraction, and browser navigation behind one API surface, instead of stitching a search API, a scraping API, and a browser automation tool together ourselves.

Yulong, Hellyeah

TinyFish covers all three, so AIMA receives the same quality of material whether the source is four static pages or a dynamic app.

How the integration works

The flow is simple, and the whole TinyFish side is API calls made at onboarding:

  • Input. The customer shares one website URL.
  • Discover. TinyFish Search finds the pages that actually explain the business, like the product pages, pricing, about, and positioning content, which often isn’t the homepage.
  • Extract. TinyFish Fetch returns those pages as clean, structured content rather than raw HTML page furniture.
  • Navigate. For sites that only reveal their context in a running browser (configurators, tabs, dynamic apps), TinyFish Web Agent clicks through and brings the content back.
  • Organize. AIMA structures the combined material into a draft Brand Profile: product and offer, target audience, value proposition, brand voice, visual identity, and destination pages.
  • Review. The customer confirms or corrects the draft, and the approved profile becomes campaign-ready context.
123456InputDiscoverExtractNavigateOrganizeReviewone URLSearchFetchWeb Agentdraft profileconfirmsCustomerTinyFish APIHellyeah
Fig 3 One URL in, an approved Brand Profile out. Steps 2 to 4 are TinyFish API calls made at onboarding. Steps 5 and 6 are ours.

The customer is the last step rather than the first. Reviewing a draft beats filling a blank form: instead of translating their company into marketing fields from scratch, they react to specific claims, correct the audience, narrow the offer, or flag a page that serves an old segment. AIMA brings the evidence. The customer adds the judgment a website can’t supply.

That review is also a visible boundary between research and approval. The customer inspects what AIMA understood before it writes a single ad, and the saved profile becomes the shared record every later stage reads from: strategy, creative, and launch review all work from the same approved context instead of asking again.

The Brand Audit screen in Hellyeah, showing the brand profile AIMA drafted from tinyfish.ai with what the company does, who it serves, its tone and value proposition, a readiness checklist and the logos and colors pulled from the site.
Fig 4 The Brand Audit screen, with the profile AIMA drafted from tinyfish.ai as the customer first sees it.

What we learned

The first surprise was how often the homepage was not the useful page. Pricing, product, and help pages usually contained the details AIMA needed. We also found old landing pages that still ranked well but described products the customer no longer wanted to promote.

Our first crawl-and-extract flow worked on simple sites and struggled with tabs, filters, configurators, and pages that loaded after a click. Better prompts could not recover missing source content. We now use Search and Fetch for straightforward pages, then Web Agent when the site needs browser navigation.

Website research can draft the profile, but it cannot choose the campaign focus. The customer still needs to select the product, audience, and offer. AIMA therefore puts the Brand Profile on screen for review before campaign work begins.

Results

Under a minuteto put a draft Brand Profile on screen
7 to 10pages read in a typical onboarding run
About a thirdof sites need Web Agent for part of the research

The full journey from signup to a launched first campaign now takes about 10 minutes, down from days or weeks.

One clean handoff

TinyFish finds, reads, and navigates the live web. We own everything after: how the approved context shapes campaign strategy, creative direction, and launch review.

01Campaign strategyThe audience and offer help AIMA frame the campaign goal, select a message, and keep the recommendation tied to the business.
02Creative directionThe value proposition, tone, logos, and colors give ad concepts a recognizable connection to the customer’s brand.
03Launch reviewThe destination pages and approved business details help the team check that the ad promise matches the experience after the click.

The customer sees none of the infrastructure. They enter a URL, review the Brand Profile, and move straight into the campaign conversation, spending their ten minutes on what to say and who to reach instead of repeating what their website already says.

If you build infrastructure that belongs in that loop, talk to us.

Find the next growth opportunity.

Tell us what you are promoting, where you are spending and what result you need. We will review the fit and come prepared for the growth audit.