Acasuso.
← All work

Market Intel – multi-client platform

Delivery status
In development
Timeframe
October 2026 → ongoing
Sample demo
Explore related demo ↗

Public demo, not access to the client’s production environment.

Today’s top opportunities in the Market Intel System sample workspace. Companies and assets are real and cited; signals, scores and people are illustrative.Open full-size image ↗
Today’s top opportunities in the Market Intel System sample workspace. Companies and assets are real and cited; signals, scores and people are illustrative.
Opportunity map in the sample workspace: who works with the target company, and the best route in, here through an existing client. Illustrative sample data, not client output.Open full-size image ↗
Opportunity map in the sample workspace: who works with the target company, and the best route in, here through an existing client. Illustrative sample data, not client output.
One workspace, several markets: opportunities, hot accounts, new signals and the share acted on per market, with a twelve-morning trend. Illustrative sample data.Open full-size image ↗
One workspace, several markets: opportunities, hot accounts, new signals and the share acted on per market, with a twelve-morning trend. Illustrative sample data.

Category: Client SaaS (multi-tenant) Status: In development Time window: October 2026 → ongoing Live URL: Private

Purpose

The point is timing: find business opportunities at the right moment, so the client is in the conversation before competitors are. For each client, a team of AI agents looks every day for custom market signals across a list of relevant online sources. The platform serves more than one client: each client has its own markets, and every weekday morning the product ranks the companies in each market, stores the top 10 with evidence and emails each member what changed.

Who it is for

Sales and business development teams at Nordic industrial suppliers.

Stack
  • Frontend: Next.js (App Router)
  • Data: Supabase with shared public facts and per-client data behind row-level security
  • Orchestration: Trigger.dev v4, weekday 06:00 Oslo
  • Email: Resend

My contribution

Designed the shared core and implemented the pipeline, scoring and delivery that every client version runs on.

Notable capabilities
  • Public business register read by municipality and size band
  • Fit rules with no model in the decision; the first failing check says why
  • Refreshes staged and committed in one transaction
  • Members of several clients switch between them

Outcome

The base every new client version is built on.

Related case study: 06-nightly-market-intel-pipeline

Skills demonstrated

multi-tenancy, row-level-security, scheduled-pipelines, public-registers

Explore another project ↗

Want to discuss the decisions behind it?

Over fifteen years of consulting and growth, and hands-on AI delivery from discovery to daily operations. I can share my CV and talk through how I connect business outcomes with systems that run.

Available for a chat. In person in Stavanger, or remotely worldwide.

Email about a job Request my CVCareer context on LinkedIn