Audited by: Delphi (MERIDIAN Infrastructure Architect)
Audit Date: 2026-03-24 Audited by: Delphi (MERIDIAN Infrastructure Architect) Website: https://rankonamazon.com Legal Entity: Rankona Mazon, LLC (Wyoming) / Rankona Mazon AB (Sweden, 559330-5773)
Rankona Mazon is a Nordic-origin, full-service Amazon agency founded in 2017 by Carl Helgesson, a Swedish entrepreneur who has been selling on Amazon since 2012. They help brands maximize sales and presence on Amazon marketplaces globally.
Key Stats:
Rankona Mazon is one piece of Carl Helgesson's broader Amazon ecosystem:
Rankona Mazon has genuine expertise but severe digital infrastructure gaps. They operate like a 2017 agency in 2026 — strong practitioner knowledge, weak tech stack, zero automation, no AI integration, and negligible inbound marketing presence. Their website gets under 5,000 monthly visits.
MERIDIAN could transform their operations across three vectors:
Estimated impact: 3-5x operational efficiency gain, significant new client acquisition capability, competitive moat vs. AI-native competitors entering the space.
File Index:
| # | File | Contents |
|---|---|---|
| 00 | 00-executive-summary.md | This file |
| 01 | 01-company-profile.md | Legal, team, history, ecosystem |
| 02 | 02-service-analysis.md | Services, methodology, pricing model |
| 03 | 03-digital-presence-audit.md | Website, SEO, social, tech stack gaps |
| 04 | 04-competitive-landscape.md | Competitors, market positioning, threats |
| 05 | 05-swot-analysis.md | Strengths, weaknesses, opportunities, threats |
| 06 | 06-meridian-value-proposition.md | How MERIDIAN helps — specific solutions mapped to gaps |
| Field | Value |
|---|---|
| US Entity | Rankona Mazon, LLC |
| Filing State | Wyoming |
| Filed | July 15, 2017 |
| Filing ID | 2017-000761529 |
| Status | Active / Good Standing |
| Registered Agent | Cloud Peak Law Group, P.C., 905 Broadway St Ste 100, Sheridan, WY 82801 |
| Registered Address | 203 S. Main St, STE 3000, Sheridan, WY 82801 (agent address, not physical office) |
| Swedish Entity | Rankona Mazon AB |
| Swedish Reg. | 559330-5773 |
| Swedish Address | Jonkopingsvaegen 15, 3tr, 331 34 VARNAMO, Sweden |
| Contact Email | [email protected] |
| Phone | +46 8 888811 |
Note: The Wyoming LLC uses a registered agent address (Cloud Peak Law Group) — a common formation service. No physical US office exists. Real operations run from Sweden.
Carl Helgesson — Swedish entrepreneur, 25+ years in sales, 20+ years as entrepreneur. Started selling on Amazon in 2012. Built 5 private label brands, successfully exited 3. Regular speaker at amaNordic and AMZSummits. Has appeared on Swedish TV, radio, and print as an Amazon expert.
``` Strategist (owns client accounts, requires own Amazon PL experience) └── Project Manager (3+ years Amazon ops, executes strategist plans) └── Associate (2+ years Amazon ops, daily execution)
Sales Representative (separate track, no Amazon experience required) ```
Internal tools: Asana (project management), Calendly (scheduling)
| Year | Event |
|---|---|
| 2012 | Carl Helgesson starts selling on Amazon |
| 2017 | Rankona Mazon LLC filed in Wyoming |
| 2021 | Swedish office opened for Nordic/European markets |
| 2023 | GDPR/Cookie policy last updated (Jan 18) |
| 2023 | Sweat Equity partnership with ICROSS announced (Apr 26) |
| 2023 | Copyright on website (not updated since) |
| Client | Category | Markets | Result |
|---|---|---|---|
| Cura of Sweden | Home & Kitchen (Weighted Blankets) | Europe & UK | 0 to EUR 5M+ in 12 months |
| Better Hockey | Sports & Outdoors (Off-ice training) | USA & Canada | 2M to 18M SEK (9x) in 12 months |
| ICROSS | Fishing watercraft | Global (Sweat Equity) | Partnership announced Apr 2023 |
"Strategic full-service agency with a holistic Amazon approach."
They position themselves not as a tools company or PPC-only agency, but as strategic partners who have "been there, done that" as Amazon sellers themselves. The core value prop: "We do what we are called — we rank your products on Amazon."
Their primary offering follows a structured methodology:
Individual services available outside the full-service engagement:
Target: VC firms and conglomerates acquiring Amazon private label brands.
Covers:
MERIDIAN relevance: This is a high-value, data-intensive service that could benefit enormously from AI-powered analysis and automated reporting.
Target: Smaller brands with great products but limited funds.
Model:
Known partner: ICROSS (Swedish Lapland fishing watercraft, announced Apr 2023)
MERIDIAN relevance: This model creates long-term recurring engagement — exactly the type of client that benefits from automated monitoring and optimization.
No pricing published anywhere on the site. Everything is consultation-based:
Market context for reference:
`` Lead discovers via: Podcast / Conference / Referral / Website └── Calendly booking (30-min free consultation) └── Analysis phase (paid or qualifying) └── Full-service engagement OR a la carte └── Ongoing optimization + expansion ``
| Gap | Impact |
|---|---|
| No self-serve tools | Can't scale beyond headcount |
| No client dashboard | Clients can't see performance in real-time |
| No automated reporting | Manual report creation for each client |
| No AI-powered optimization | All keyword research, listing optimization is manual |
| No competitive monitoring | No automated alerts when competitors change listings/pricing |
| No content pipeline | No blog, no thought leadership engine beyond podcast |
| No CRM visible | Lead management likely in spreadsheets or basic tools |
| No case study depth | Only 2 case studies, no video testimonials, no detailed metrics |
Their methodology is sound but manual. Every phase of their 7-step process has well-understood AI/automation solutions available today that they aren't using. A competitor with the same methodology but AI-augmented execution would operate at 5-10x their throughput with fewer staff.
| Component | Details |
|---|---|
| CMS | WordPress 6.9.4 |
| Theme | Divi 4.22.2 (Elegant Themes page builder) |
| Hosting | Google Cloud Platform (IP: 35.209.58.72) |
| Web Server | nginx |
| Analytics | Google Analytics (G-P76L0ZJZQ3) |
| Chat | Tawk.to (property: 63c71a9ac2f1ac1e202e3488) |
| Scheduling | Calendly (calendly.com/rankona-mazon) |
| Forms | Contact Form 7 v6.1.5 |
| Popups | Popup Maker v1.21.5 |
| Fonts | Raleway, Mukta (Google Fonts) |
| Brand Colors | #f6aa22 (gold), #1a1717 (dark), #ffffff (white) |
`` rankonamazon.com/ ├── / (homepage) ├── /about/ ├── /our-services/ ├── /why-us/ ├── /why-amazon/ ├── /our-work/ (case studies) ├── /careers/ ├── /contact/ ├── /gdpr/ └── /cookie-policy/ ``
Total live pages: 10 404s found: /about-us, /services, /pricing, /blog, /case-studies, /results, /faq, /privacy-policy
| Element | Status | Impact |
|---|---|---|
| Meta descriptions | MISSING on all pages | Google generates snippets randomly from page content |
| Open Graph tags | MISSING | Social shares show no preview image/description |
| Schema.org / JSON-LD | MISSING | No rich snippets in search results |
| XML Sitemap | Not verified | May exist at /sitemap.xml but not linked |
| Blog / Content | DOES NOT EXIST | Zero organic content marketing |
| Alt text on images | Not verified | Likely missing given other gaps |
| Canonical tags | Present | One thing they got right |
| Robots meta | max-image-preview:large | Acceptable |
An Amazon SEO agency that doesn't do SEO on their own website. They help clients rank on Amazon but have:
This is either intentional (they rely entirely on referrals/podcast/conferences) or a significant blind spot.
| Issue | Risk |
|---|---|
| XML-RPC enabled | Brute force vector, DDoS amplification |
| WordPress REST API exposed | User enumeration, content scraping |
| Pingback enabled | DDoS amplification attacks |
| jQuery (deferred) | Depends on version — may have known vulnerabilities |
| Divi 4.22.2 | Should be verified against latest security patches |
SimilarWeb: No data available — site falls below the ~5,000 monthly visits threshold.
Assessment: The site receives very low organic traffic. Client acquisition is driven by:
| Element | Implementation |
|---|---|
| CTA: Schedule Meeting | Calendly embed — present on most pages |
| CTA: Contact Us | Contact Form 7 on /contact/ |
| CTA: Download eGuide | "8 Success Factors" lead magnet on /about/ |
| Newsletter signup | Form with Name, Email, Company, Brand details, file upload |
| Live chat | Tawk.to widget (persistent) |
| Sweat Equity application | Popup form |
| Career application | Popup form |
| Element | Impact |
|---|---|
| No email automation | No nurture sequences after lead capture |
| No retargeting pixels | No Facebook/LinkedIn/Google remarketing |
| No chatbot | Tawk.to is live-only, no automated responses |
| No pricing calculator | No self-serve qualification |
| No video content | No explainers, testimonials, or demos |
| No trust badges | No partner logos, certifications, or awards displayed |
| No social proof widgets | No review aggregators or testimonial sliders |
| No exit intent | No popups when users leave |
| Platform | Status |
|---|---|
| Trustpilot | No profile |
| G2 | No profile |
| Clutch | No profile |
| BBB | No profile |
| Glassdoor | No reviews |
| No mentions | |
| Google Reviews | Not verified |
Zero independent validation of their claims exists in any public review database.
| Dimension | Score | Notes |
|---|---|---|
| Website quality | 4/10 | Clean design, but missing SEO fundamentals |
| Content marketing | 1/10 | No blog, no content strategy |
| Social media | 1/10 | Essentially non-existent |
| SEO | 2/10 | No meta tags, no structured data, no content |
| Conversion optimization | 3/10 | Has CTAs but no automation or nurturing |
| Security | 4/10 | Standard WordPress, some exposed vectors |
| Analytics | 3/10 | GA4 exists, but no visible optimization loop |
| Overall | 2.5/10 | Severe digital infrastructure deficit |
Amazon Seller Services Market: Expected to reach $2.6 billion by 2033 (9.5% CAGR).
Active Amazon sellers: Dropped from 2.4M (2021) to 1.65M (end 2025) — consolidation is accelerating. Remaining sellers are more sophisticated, more likely to hire agencies, and more demanding of results.
Key trend: Most top-performing sellers now partner with agencies. The DIY era is ending for serious brands.
| Agency | Scale | Differentiation | Threat Level |
|---|---|---|---|
| My Amazon Guy | $6B+ in client sales claimed | Content marketing machine (YouTube), large team | High — dominates inbound |
| Canopy Management | Premium tier | White-glove service, enterprise clients | Medium — different segment |
| Acadia (fka Bobsled) | ~150 staff, 6 acquisitions | Roll-up strategy, institutional backing | High — consolidating market |
| SalesDuo | AI-powered, 85% ex-Amazon staff | AI differentiation, insider knowledge | High — tech + talent moat |
| 9AM | $250M+ in managed ad spend | PPC specialization at scale | Medium — different focus |
| Agency | Niche | Overlap with Rankona |
|---|---|---|
| Rank N Bank (James Hyatt) | Amazon PPC, San Diego | Similar name confusion risk |
| ANavigator | 8-figure client growth | Similar positioning |
| Amazon Growth Lab | Operator-creative hybrid | Similar practitioner angle |
| WebFX | Large digital agency with Amazon division | Scale advantage |
| OuterBox | Amazon SEO specialist | Direct service overlap |
| Tool | Price | What It Replaces |
|---|---|---|
| Helium 10 | From $29/month | Keyword research, listing optimization, competitor tracking |
| Jungle Scout | From $29/month | Product research, market analysis |
| AMZScout | Budget tier | Basic product/keyword research |
| Perpetua | Mid-tier | Amazon SEO automation |
| DataHawk | Enterprise | Analytics and monitoring |
Threat from tools: Self-serve tools increasingly replace the analysis and keyword research phases that agencies charge thousands for. Agencies that don't offer value beyond what Helium 10 provides are losing relevance.
New agencies are launching with AI-first approaches:
Rankona Mazon has zero AI capabilities. Every task is manual. This will become an existential threat within 12-18 months as clients expect AI-powered insights as table stakes.
Amazon continues to expand Seller Central's built-in capabilities:
These erode the value of basic agency services, pushing agencies toward strategic advisory and advanced optimization.
The Acadia model — acquiring smaller agencies — is a direct threat. Well-funded roll-ups can offer broader services, deeper tech, and more competitive pricing through economies of scale.
`` HIGH TECH CAPABILITY │ SalesDuo ● │ ● Helium 10 (self-serve) │ Acadia ● │ ● Perpetua │ ──────────────────────┼────────────────────── LARGE SCALE │ SMALL/NICHE │ My Amazon Guy ● │ │ ● Rankona Mazon (HERE) Canopy ● │ │ ● Amazon Growth Lab │ LOW TECH CAPABILITY ``
Rankona Mazon sits in the bottom-right quadrant — small scale, low tech. This is the most vulnerable position. They survive on practitioner credibility and Nordic market lock-in. Without tech investment, they will be squeezed by both tool companies (from above) and larger agencies (from the left).
Despite the threats, the timing is actually favorable for Rankona Mazon IF they invest in technology:
The question is whether they invest in tech before the window closes.
75% of staff have launched their own Amazon private label brands. Carl Helgesson personally built and exited 3 brands since 2012. This is not a "we read about Amazon" agency — they have battlefield experience. Most competitors hire marketers; Rankona hires sellers.
Carl Helgesson has constructed a full ecosystem:
A Nordic brand wanting Amazon help encounters Helgesson at every touchpoint. This flywheel is genuinely hard to replicate.
Deep knowledge of pan-European Amazon operations: multi-marketplace strategy, VAT compliance, cross-border FBA logistics, localized listings. This is complex and valuable.
No proprietary tools, no AI, no automation, no dashboards. Everything is manual. In 2026, this is a critical vulnerability. Competitors with AI-powered listing optimization can produce in minutes what Rankona's team takes hours to create.
The entire brand is Carl Helgesson. The podcast, the conference, the media appearances, the speaking engagements — all one person. If Helgesson steps back, the acquisition engine stalls.
11-50 employees serving clients manually. Growth requires linear headcount increase. No leverage through technology or automation.
"Rankona Mazon" is phonetically similar to "Rank on Amazon" which is generic/descriptive. "Rank N Bank" is a competitor with a similar name. The brand isn't distinctive or protectable.
Copyright says 2023. Cookie policy references unrelated websites. Contact email uses amanordic.com instead of rankonamazon.com. These signal neglect.
Every phase of their 7-step methodology can be AI-augmented:
They have the expertise to create world-class Amazon content but produce zero written content. A blog covering Amazon selling strategies, marketplace updates, and case studies could drive significant organic traffic.
The Nordic ecosystem is strong but the English-language presence is weak. With proper content and SEO, they could compete for English-speaking clients across US, UK, Australia, and pan-European markets.
The due diligence service is positioned for a growing market. Amazon aggregators (Thrasio model) are still active, and traditional PE/VC firms increasingly acquire DTC brands with Amazon channels. This service could become a major revenue line.
KNAA graduates are pre-qualified leads for agency services. This pipeline could be systematized with automation: training completion → assessment → agency upsell with tailored recommendations.
Amazonpodden has audience but no visible monetization or English-language distribution. Transcription, translation, and repurposing could multiply reach.
New agencies launching with AI-first approaches will offer faster, cheaper, and more data-driven services. Without tech investment, Rankona becomes a premium-priced manual alternative competing against automated solutions.
Helium 10, Jungle Scout, and Amazon's own tools keep improving. The analysis and keyword research phases — which Rankona charges for — become commoditized. Agencies must deliver value beyond what tools provide.
Funded acquirers (Acadia model) are buying agencies. A Nordic-focused agency with genuine expertise but no tech moat is exactly the kind of acquisition target that gets absorbed — or outcompeted by the combined entity.
Amazon continuously changes its algorithms, advertising options, and seller policies. Without automated monitoring, Rankona learns about changes reactively rather than proactively.
Brands increasingly expect real-time dashboards, AI-powered insights, and automated reporting. Manual PDF reports delivered monthly will feel archaic to clients comparing agencies.
Single point of failure. No visible succession planning. The ecosystem (podcast, conference, training, agency) is all Carl Helgesson.
The SWOT reveals a company with strong expertise trapped in weak infrastructure. The strengths (practitioner knowledge, Nordic lock-in, unique service models) are durable and hard to copy. The weaknesses (no tech, no content, no social proof) are all solvable with the right technology partner.
The window for action is narrow. AI-native competitors are entering the Amazon agency space now. Within 12-18 months, the gap between tech-enabled and manual agencies will become obvious to clients. Rankona Mazon must decide: invest in technology now, or get acquired/marginalized.
This is exactly where MERIDIAN creates value.
Rankona Mazon has expert-grade Amazon knowledge running on intern-grade infrastructure. MERIDIAN bridges that gap — delivering AI-powered operational infrastructure that multiplies their practitioner expertise without replacing it.
Their gap: Manual listing creation across 7 marketplaces, each requiring localized copy, keyword research, and A9 algorithm compliance. A single "Perfect Listing" takes hours of human work.
MERIDIAN solution:
Impact: 10x listing production speed. Staff shifts from creation to quality review and strategic decisions.
Their gap: No automated competitor tracking. Changes in competitor pricing, listings, reviews, and ad positioning are discovered manually — or not at all.
MERIDIAN solution:
Impact: From reactive to proactive. Clients see Rankona as having "eyes everywhere" — a capability only tech-enabled agencies can deliver.
Their gap: No client-facing dashboard. Reporting is manual (presumably slide decks or PDFs delivered periodically).
MERIDIAN solution:
Impact: Client retention increases (they can see value continuously, not just at monthly reviews). Reduces manual reporting workload by 80%+.
Their gap: No visible CRM. Leads from Calendly, Contact Form 7, Tawk.to chat, podcast, and conferences likely flow into email or spreadsheets.
MERIDIAN solution:
Impact: No lead falls through the cracks. Conversion rate from inquiry to client increases significantly. The training-to-agency pipeline becomes systematized.
Their gap: Zero content marketing. No blog, no articles, no SEO-optimized content despite having deep Amazon expertise.
MERIDIAN solution:
Impact: From invisible to discoverable. Inbound leads become a real channel. The podcast content (which already exists) gets multiplied across formats.
Their gap: Missing meta descriptions, no Schema.org markup, no OG tags, no structured data, stale copyright, security vulnerabilities.
MERIDIAN solution:
Impact: Foundation for all other digital efforts. Without this, content marketing and inbound lead generation can't work.
Their gap: Manual PPC management. No automated bid optimization, no predictive budget allocation.
MERIDIAN solution:
Impact: Better ad performance with less manual management. Strategists focus on strategy, not bid spreadsheets.
Their gap: Amazon brand due diligence is their highest-value niche service, but it's entirely manual research.
MERIDIAN solution:
Impact: Due diligence reports that take weeks become available in days. Higher throughput = more DD engagements = more revenue from the growing Amazon M&A market.
Build the core systems (dashboard, CRM, monitoring) as a one-time project. Hand off to Rankona's team to operate.
MERIDIAN builds and operates the AI layer as an ongoing service. Rankona focuses on client strategy; MERIDIAN handles the technology.
Mirror Rankona's own model — MERIDIAN takes equity in Rankona Mazon in exchange for building the complete technology stack. Aligned incentives.
MERIDIAN builds a white-labeled Amazon agency platform that Rankona resells to their KNAA graduates and smaller clients. Creates a SaaS revenue line.
If Rankona Mazon were to engage MERIDIAN, the recommended implementation order:
``` Phase 1 (Weeks 1-4): Foundation ├── Website SEO remediation ├── CRM setup + lead capture unification └── Basic competitive monitoring (top 5 competitors per client)
Phase 2 (Weeks 5-8): Client Value ├── Client dashboard MVP ├── Automated reporting └── PPC intelligence layer
Phase 3 (Weeks 9-12): Growth Engine ├── Content marketing pipeline (podcast → blog → social) ├── AI listing optimization engine └── Lead nurture automation
Phase 4 (Weeks 13-16): Differentiation ├── Due diligence automation ├── Advanced competitive intelligence └── White-label platform (if Option D) ```
Rankona Mazon has something most Amazon agencies fake — real seller experience. But in 2026, expertise without technology is a knife at a gunfight. Your competitors are deploying AI for listing optimization, automated competitive monitoring, and real-time client dashboards while your team does everything manually. MERIDIAN doesn't replace your Amazon knowledge — it multiplies it. We build the AI infrastructure that lets your 20-person team operate like a 100-person agency: automated reporting, intelligent monitoring, LLM-powered listings, and a content engine that turns your podcast expertise into inbound leads. Your methodology is proven. Let us give it the technology it deserves.
| Quick Win | Effort | Impact |
|---|---|---|
| Add meta descriptions to all 10 pages | 2 hours | Immediate SEO improvement |
| Add Schema.org Organization markup | 2 hours | Rich snippets in search |
| Disable XML-RPC | 30 min | Security hardening |
| Add OG tags for social sharing | 1 hour | Better social previews |
| Update copyright to 2026 | 5 min | Credibility signal |
| Fix cookie policy (remove unrelated sites) | 15 min | Professional appearance |
| Add social media links (or create profiles) | 1 day | Digital presence foundation |
| Set up Trustpilot profile | 1 hour | Begin collecting reviews |
| Create LinkedIn content calendar | 1 day | Start social presence |
| Transcribe 5 podcast episodes → blog posts | 3 days | Instant content marketing |
Use these prompts with Claude deep research, Perplexity Pro, or Gemini Deep Research to fill gaps in our audit.
Research Carl Helgesson's full professional history. Track his Amazon selling career from 2012 to present — which brands did he build, which 3 did he exit, what categories were they in, what were the approximate exit values? Find any interviews, podcast appearances (outside Amazonpodden), conference talks, or media features. Map his LinkedIn network — who are his closest professional connections? Has he raised any funding or taken on investors for Rankona Mazon, KNAA, or amaNordic? Is there any connection to "amanordic.com" beyond the shared email domain?
Identify current and former Rankona Mazon employees. Search LinkedIn for people who list Rankona Mazon, KNAA, or amaNordic as current or past employers. What are their roles, locations, and backgrounds? How many are based in Sweden vs. Pakistan vs. Philippines vs. other countries? Are the offshore team members doing execution (listing creation, PPC management) while Swedish/US staff handle strategy and sales? Have any former employees posted about their experience? What does the actual headcount look like vs. the "11-50" estimate?
Deep dive into KNAA (Komplett Nordisk Amazon Akademi). What is the curriculum? What does the 8-week program cover? What is the price? How are graduates supported after completion? What is the conversion rate from KNAA graduate to Rankona Mazon agency client? Find any KNAA graduate testimonials, reviews, or social media posts about their experience. Is KNAA still actively enrolling, or has it paused? What platform do they use for course delivery? How does KNAA compare to other Amazon seller training programs (Amazing Selling Machine, Marketplace Superheroes, Helium 10 Freedom Ticket)?
Find all Rankona Mazon clients beyond Cura of Sweden and Better Hockey. Search for brands that mention Rankona Mazon, Carl Helgesson, or "rankonamazon" in any context — press releases, social media, Amazon listings credits, conference testimonials. What is ICROSS's current Amazon presence after the Sweat Equity partnership (announced Apr 2023)? Are Cura of Sweden's Amazon listings still ranking well? Has Better Hockey maintained its 9x growth? What Amazon categories do their clients cluster in? Estimate total number of active clients.
Research Amazon agency pricing models and estimate Rankona Mazon's positioning. What do comparable Nordic/European Amazon agencies charge? What is the typical retainer range for a full-service Amazon agency with 11-50 employees? How does the Sweat Equity model work financially — what equity percentage do they typically take? What is the revenue split between agency services, KNAA training, and amaNordic conference? Are there any public financial filings for Rankona Mazon AB (Swedish company 559330-5773) available through Swedish business registries (Bolagsverket, Allabolag.se)?
Map the amaNordic conference ecosystem. When and where are events held? How many attendees? Who sponsors? What is the ticket price? Who are the other speakers besides Helgesson? Is it profitable as a standalone business or primarily a lead generation channel for KNAA and Rankona Mazon? Find any attendee reviews, social media posts, or recap articles from 2022, 2023, and 2024 events. Has a 2025 or 2026 event been announced?
Map the competitive landscape for Amazon agencies serving Nordic/Scandinavian brands. Who else serves Swedish, Norwegian, Danish, and Finnish brands wanting to sell on Amazon? Are there local Nordic competitors, or do brands typically hire US/UK agencies? What is the total addressable market — how many Nordic brands are currently selling on Amazon, and how many could be? What are the unique challenges of Amazon selling for Nordic brands (VAT, logistics, language, marketplace selection)? How does Amazon's presence in Sweden (amazon.se, launched 2020) change the landscape?
Analyze the current state of Amazon brand acquisitions and how Rankona Mazon's due diligence service fits. What happened to the aggregator boom (Thrasio, Perch, Heyday, etc.)? Who is still actively acquiring Amazon brands in 2025-2026? What do acquirers pay for due diligence services? What does a typical Amazon brand DD report cover? Are there specialized DD firms, or do agencies like Rankona handle this ad hoc? What is the deal volume and average deal size for Amazon FBA brand acquisitions in the EU/Nordic region specifically?
What technology stack do leading Amazon agencies use in 2026? Map the tools ecosystem: which agencies have built proprietary platforms vs. using third-party tools (Helium 10, Jungle Scout, Pacvue, Perpetua, Quartile, Teikametrics)? What AI/ML capabilities are becoming standard for Amazon agencies — automated listing optimization, predictive analytics, automated bidding, review analysis? Are there white-label Amazon agency platforms available? What would it cost for Rankona Mazon to build vs. buy a modern tech stack? What are the Amazon Advertising API and SP-API capabilities that enable automation?
Investigate the regulatory and compliance landscape for Amazon agencies. Are there any FTC, EU, or Swedish regulatory actions against Amazon agencies for fake reviews, ranking manipulation, or deceptive practices? What are Amazon's Terms of Service regarding "ranking services" — is any of what Rankona does against Amazon TOS? Has Amazon taken enforcement action against agencies? What is the legal risk profile of offering "Launch & Rank" services? Are there any pending or past legal disputes involving Rankona Mazon, Carl Helgesson, KNAA, or amaNordic?
Pull all available financial and corporate data for Rankona Mazon AB (559330-5773) and KNAA AB from Swedish registries. Check Allabolag.se, Bolagsverket, Ratsit, and Hitta.se for: annual reports (årsredovisning), revenue figures, profit/loss, number of employees, board members, beneficial owners, any registered liens or notes. Also check if Carl Helgesson has other registered Swedish companies. What is the relationship between the Wyoming LLC and the Swedish AB — is one a subsidiary of the other?
Analyze Amazonpodden's reach and content. How many episodes have been published? What is the average episode length? What topics are covered most frequently? Can you estimate listener numbers from Spotify charts or rankings? Who are the guests? Is the podcast monetized (sponsors, ads)? How does it compare to other Amazon-focused podcasts in reach and quality? Is there an English-language version or any plans to expand beyond Swedish? What are the most popular/downloaded episodes?
Investigate whether Rankona Mazon runs any paid advertising. Check Facebook Ad Library for active or historical ads. Search Google Ads transparency center. Are they running LinkedIn ads? Any display advertising detected through ad network databases? If they're not running paid ads, how are they acquiring clients beyond organic/referral channels? What is the estimated customer acquisition cost for an Amazon agency in this market segment?
Map Rankona Mazon's partnership and referral network. Do they have formal partnerships with Amazon (Amazon SPN — Service Provider Network)? Are they an approved Amazon Ads partner? Do they partner with any complementary service providers (logistics, photography, brand protection)? Are they listed in any agency directories? Do they have referral agreements with Helium 10, Jungle Scout, or other tool companies? What conference speaker networks is Helgesson part of?
Research what makes Amazon brands switch agencies or hire their first agency. Survey Reddit (r/FulfillmentByAmazon, r/AmazonSeller), Facebook groups, and forums for: What frustrations do brands have with current Amazon agencies? What triggers the decision to hire an agency? What are the top reasons for firing an agency? What do brands wish their agency did better? What is the typical evaluation process — do they compare 2-3 agencies, request proposals, do trials? How important is practitioner experience (the agency having sold on Amazon themselves) vs. scale and technology?
Date: Friday, March 27, 2026 Prepared by: Delphi (MERIDIAN) Classification: Internal — do not share with prospect
Carl Helgesson — Swedish entrepreneur, Amazon seller since 2012. Built 5 private label brands, exited 3. Founder of:
Company: 15-25 employees across 8 countries. Sub-$5M revenue. Amazon EU Tier 1 Platinum Partner (Feb 2025). Recently partnered with Humble Group (publicly traded, 40+ brands).
Carl requested this meeting. Our audit was built for outbound — but this is inbound. That changes posture from "pitch" to "diagnose." Don't present problems. Ask what he's trying to solve.
"We've been following your work — the Tier 1 Platinum status, the Humble Group deal, the ecosystem you've built. Most agencies have marketing and no substance. You have substance and no marketing. We think that's a solvable problem."
Then listen. His response tells us everything.
| # | Question | What It Reveals |
|---|---|---|
| 1 | "What prompted you to reach out now?" | The trigger — whatever he says first is the real priority |
| 2 | "How are you managing client reporting today?" | If slide decks/PDFs, dashboard is the wedge |
| 3 | "What's your biggest bottleneck to taking on more clients?" | Capacity (tech solves) vs. pipeline (marketing solves) |
| 4 | "Have you looked at what AI-native agencies are offering?" | Whether competitive threat is on his radar |
| 5 | "What would make this a great use of your time today?" | Let him define the meeting — reduces builder's bias |
His 44 Swedish podcast episodes = 88-132 English blog posts sitting untouched. We transcribe, translate, optimize for SEO, and publish. Turns his existing IP into inbound leads across English-speaking markets.
Demo hook: "Pick one episode — we'll show you the finished output before we leave."
Fix in hours what's been broken since 2023:
Why free: Shows we deliver, not just talk. Builds trust for paid work.
Client dashboard, CRM, AI listing optimization, ad intelligence, due diligence automation — all documented in our audit but do not lead with these. Match proposal scale to a sub-$5M company.
| Gap | Severity | Evidence |
|---|---|---|
| No blog, no content marketing | Critical | Zero articles, zero SEO content |
| No meta descriptions, no Schema.org | High | Verified from site HTML |
| Website frozen since Jan 2023 | High | wp-json modification dates |
| Zero reviews on Trustpilot/G2/Clutch | High | Searched all platforms |
| No social media presence | High | No linked accounts on site |
| No email automation after lead capture | Medium | No nurture sequences |
| Cookie policy references wrong domains | Low | Template not customized |
Do NOT present this as a list of failures. Use individual data points only if the conversation calls for them.
| Topic | Guidance |
|---|---|
| EUR 1.06B sales claim | Don't cite or challenge. Methodology unclear (lifetime, all activities). |
| "85 years" vs "100 years" experience | Their contradiction. Don't mention unless relevant. |
| Admin email leak ([email protected] in wp-json) | Shows deep research but feels invasive. Use only if discussing security. |
| Swedish business culture | Relationship-first. Don't rush to close. Build trust over transactions. |
| His success without tech | He landed Humble Group and Platinum status with a 2.5/10 website. Lead with respect, not critique. |
| Role | Person | Responsibility |
|---|---|---|
| Lead | TBD | Drives conversation, asks discovery questions |
| Note-taker | TBD | Captures key answers, action items, next steps |
| Demo | TBD | Ready to show content pipeline output or quick win examples if conversation goes there |
Full audit package: audits/prospect-audits/rankonamazon/ (7 files + coherence audit)
Date: Thursday, April 3, 2026 — 3:00 PM CET Prepared by: Delphi (MERIDIAN) Duration: 60 minutes (30-minute compressed version at end) Attendees (expected): Carl Helgesson + 1-2 strategists
This is not a product demo — it is a proof-of-research meeting. Carl has already called this "the most impressive" AI solution he's seen. The bar is not novelty. The bar is specificity: did you actually understand his business, or are you giving the same deck to every Amazon agency?
Every minute of the demo should answer the question Carl is silently asking: "Is this worth interrupting a $100M buildout for?"
Our posture: Infrastructure architects, not vendors. We build the machine that runs his vision. He stays expert. We build the leverage.
| Item | Status | Owner |
|---|---|---|
| Screen share working (no full-screen lag) | Confirm day-before | Alexander |
| MIG knowledge graph loaded with Rankona nodes | Build by April 2 | Ely Beckman |
| Proposal automation demo environment ready | Build by April 2 | Ely Beckman |
| Alert triage mock dashboard loaded | Build by April 2 | Ely Beckman |
| KNAA bot prototype (even wireframe) | Build by April 2 | Alexander |
| Architecture slide (federated mesh, data ownership) | Build by April 2 | Alexander |
| Fallback: static screenshots if live demo fails | Prepare April 2 | Ely Beckman |
| Backup laptop charged | Day-of | Alexander |
| Zoom/Meet link tested with audio | 30 min before | Alexander |
Goal: Make Carl feel seen. Not pitched. Seen. Establish that we understand his ecosystem better than most people he talks to professionally.
Open directly into the MIG knowledge graph visualization — not a slide deck. The first thing they see is a graph, not a PowerPoint. Nodes visible: Carl Helgesson, Rankona Mazon, KNAA, amaNordic, Amazonpodden, Humble Group, Cura of Sweden, Better Hockey, and — critically — nodes extracted from the sales call itself.
Point to the call-derived nodes explicitly: "The 43,400-SKU client is already in here. The 44-hour proposal bottleneck is in here. We extracted this from our conversation."
Then show the digital presence audit summary — briefly, as context. Not to embarrass. To establish depth.
"Before we show you anything about MERIDIAN, we want to show you what we found. After our call, we ran a full research pass on Rankona Mazon — company structure, service methodology, competitive position, digital presence, the whole ecosystem you've built. What we found isn't a list of problems. It's a map of leverage. [Open graph.] This is the knowledge graph MERIDIAN built from your business. These aren't fields in a CRM — these are entities and relationships. Carl Helgesson sits here. Rankona Mazon branches into KNAA, amaNordic, the podcast. The Humble Group deal is here. Your Tier 1 Platinum status is here. And these nodes — [point to call-derived nodes] — came directly from our conversation. The 43,400-SKU client. The 44-hour forecast problem. The six tools that don't talk to each other. We stored those as structured intelligence before we built a single slide. This is the same thing we'd build for your business: a persistent, queryable understanding of your clients, your competitors, and your market — that gets smarter over time."
"You came to us with specific problems. Let's go through them — not to sell you a system, but to show you what solving each one actually looks like."
Goal: Map each of Carl's stated pain points to a concrete MERIDIAN capability. Show, don't tell. Each section is 4-5 minutes. Move fast.
"44 hours → under 4 hours"
What to Show:
Open the proposal automation demo. Input on the left: a brief (client name, category, current revenue, target markets, competitor ASINs, growth target). Output on the right: a structured forecast proposal — market sizing, keyword opportunity, PPC budget model, launch roadmap, projected revenue curve.
Show the agent chain in abbreviated form: input → research agent (pulls category data, competitor analysis) → financial model agent (builds forecast) → narrative agent (writes the proposal prose) → output document.
What to Say:
"You told us one forecast took 44 hours. We ran that number against your stated pipeline. If you close 40% of qualified prospects — and you're about to bring on a 43,400-SKU client — that 44-hour ceiling becomes the thing that kills your growth, not your team's capability. Here's the MERIDIAN proposal pipeline. [Show input brief.] Your strategist fills out a brief like this — takes 20 minutes. A multi-agent chain handles the research pass, the financial modeling, and the narrative construction. [Show output.] What comes out is a structured forecast proposal ready for senior review. You're not removing the strategist. You're removing the 38 hours of undifferentiated research work. They review and refine. They don't reconstruct from scratch. For a 43,400-SKU portfolio, the analysis alone would have taken weeks. In this model, it's an overnight run."
What NOT to Say:
"6 siloed tools → one MIG brain"
What to Show:
The knowledge graph again, but zoomed into the tool integration layer. Show conceptual nodes for: Helium 10, Jungle Scout, Seller Central, AMS (advertising console), Asana, whatever reporting tool they currently use. Show MERIDIAN as the hub that ingests from all of them. Then show a single query: "What are the top 3 threats to Client X's Buy Box position right now?" — and the answer pulls from three sources.
What to Say:
"You mentioned six tools that don't talk to each other. Every tool is generating signal. The problem is no one is synthesizing it. Helium 10 sees keyword rank changes. Seller Central sees inventory levels. Your advertising console sees ACoS degradation. No single person has all three open at the same time, every day, for every client. MERIDIAN's memory layer — the MIG — becomes the persistent synthesis point. When we pull data from all six tools, we're not building another dashboard. We're building a knowledge graph that can be queried in plain language. Your strategist doesn't open six tabs. They ask: 'What does Client X need attention on this week?' The system answers with structured reasoning, not raw data."
What NOT to Say:
"1,000+ SKU monitoring → daemon prioritization"
What to Show:
The mock alert triage feed. Scroll through it at realistic speed — don't freeze on one item. Show severity scoring: Critical (suppressed listing, buy box lost to hijacker), High (BSR dropped 15% in 48 hours), Medium (ad budget pacing 40% under target), Low (listing image flagged for review). Then show the prioritized action queue: what the on-call strategist sees first, second, third.
Point out explicitly: "The daemon ran this at 3 AM CET. Your team saw it at 8 AM with a prioritized queue, not a raw alert log."
What to Say:
"At 1,000 SKUs, monitoring is not a human job. It's a math problem. There are approximately 8,760 hours in a year. A team member checking 1,000 SKUs manually, even at 30 seconds per SKU, spends 8 hours a day doing nothing but looking for problems. MERIDIAN runs persistent monitoring daemons. They watch every SKU, 24/7. They don't get tired, they don't miss a shift, and they don't need to be taught what a suppressed listing looks like. [Show the triage feed.] This is what a strategist sees when they open their dashboard Monday morning after a weekend. Not a 200-row spreadsheet. A prioritized queue: three criticals, two highs, everything else can wait. They spend the first 30 minutes of their day on the three things that actually matter. For your 43,400-SKU client — this isn't a feature. It's a prerequisite."
What NOT to Say:
"AI drafts + translation memory"
What to Show:
A side-by-side: one product listing in English (with proper keyword density, A9-compliant structure, character limits respected) and four variants — SE, DE, FR, NL — with shared brand terminology highlighted in each. Then show the translation memory concept: a term like "breathable microfiber" in English maps to approved translations in each market, stored and reused across every listing.
What to Say:
"This one connects directly to the 43,400-SKU client. At that scale, listing creation becomes a language problem, not just a strategy problem. If even 10% of those SKUs need localized listings across four European markets, you're looking at 17,000 individual listing variants. Your team cannot write those. No team can. MERIDIAN's content pipeline does three things: it generates A9-compliant listing copy from a product brief, it maintains a translation memory so brand terminology is consistent across every language, and it flags listings that fall below quality thresholds — character limits exceeded, missing backend keywords, keyword stuffing. Your strategists define the standards. The system executes to them, consistently, at scale. Quality review drops from hours per listing to minutes."
What NOT to Say:
"Everything we've shown so far applies to the agency operations side. But you have another business — and it's actually where I think the most interesting opportunity lives. KNAA."
[Pause. Let that land before moving.]
Goal: Spark Carl's imagination around the education business. This act should be aspirational, not technical. It's the one moment in the demo where you're selling a vision, not a system.
A simple wireframe or concept screen (not a working product). It should show:
Then show the concept architecture briefly: 335 lessons → knowledge base → bot prompt layer with Carl's voice → 24/7 student support.
What to Say:
"You have 200+ students who went through KNAA. 335 lessons. You personally teach a framework that took you a decade to build. But the most valuable thing you teach isn't the framework — it's the judgment calls. What do you do when your launch isn't working? What's the real reason a listing isn't converting? How do you know when to cut a product? Those answers live in your head. Right now, students access them once a week in a group session, or not at all. What we're calling Carl Bot — [show wireframe] — is a 24/7 KNAA assistant that answers in your voice, drawing on your course curriculum. A student at 11 PM on a Tuesday, panicking because their launch is tanking, gets a response that sounds like you, draws on the Week 4 lesson on launch velocity, and tells them exactly what to check. You're not replaced. You're multiplied. Your judgment becomes accessible to every student, at any hour, in any timezone. For the training business, this has a direct impact on your NPS — which is already 9.86. Imagine what happens when students have you available every time they're stuck."
"Before we talk about what a relationship looks like, I want to be direct about one thing Carl asked on our last call — data ownership. This is the architecture answer, not the sales answer."
Goal: Answer Carl's specific questions from the intro call (data ownership, exit implications) with technical specificity, not reassurances. He understands technical concepts — treat him accordingly.
A single architecture diagram (not a complex engineering diagram — a clean conceptual one). Three layers visible:
Show the federated mesh concept: Rankona Mazon gets a dedicated subgraph. It is logically and optionally physically separated from other clients. Carl's 43,400-SKU client's data is not co-mingled with another agency's client data.
Show the SOC2 posture briefly: encrypted in transit (bolt+ssc, TLS), encrypted at rest, Tailscale-only internal access (no public ports), audit trail on every write operation.
What to Say:
"Carl, you asked two specific questions on our call: who owns the data, and what happens at exit. On ownership: the data you put into MERIDIAN is yours. Not licensed to us, not aggregated into a shared model, not used to train anything without explicit agreement. Your Rankona client graph is a private subgraph. It does not interact with any other client's data. If you terminate the relationship, you get a full export — every node, every relationship, every piece of stored intelligence — in a portable format. [Show architecture diagram.] This is the federated mesh model. Your instance runs as an isolated node in the MERIDIAN network. We can process data for you without having unrestricted access to it. You can verify that at any time. On exit implications — you raised this in the context of your $100M goal. The architecture is specifically designed for this. If you sell Rankona Mazon, the buyer gets the system too. The intelligence you've built into MERIDIAN — client histories, competitive data, operational workflows — becomes part of your enterprise value, not a liability that the buyer has to untangle. In due diligence, a documented AI system with structured data is an asset. An undocumented collection of spreadsheets is a risk. On image quality — the content pipeline outputs link to original assets. We don't compress or transcode proprietary creative. What you put in is what comes out. On SOC2 posture: we're building toward certification. The architecture is zero-trust by design — no public ports open, everything routed through encrypted tunnels, audit trail on every data write. If you have an enterprise client who runs their own security review, we can walk through the architecture with their team."
"Last piece. What does this actually look like to get started, and what does it mean for where you're trying to take this business."
Goal: Give Carl a clear, low-friction entry point. Do not present 4 engagement options — present one recommended path with one alternative. Anchor on his exit goal. End with a specific next step, not an open-ended "let us know."
A single page (not a full proposal deck). Three columns:
| **Pilot (4 weeks)** | **Build-Out (12 weeks)** | |
|---|---|---|
| Scope | Proposal automation + alert triage for 1 client | Full stack (all 4 pain points) |
| What you get | Proof of time savings, measurable output | Production system |
| Your commitment | 1 strategist as pilot partner, 4 hrs/week | Dedicated ops contact |
| Our commitment | Weekly check-ins, full documentation | Full build team |
| Pricing model | Usage-based (API costs + build fee) | TBD based on pilot learnings |
Then anchor the valuation multiplier story (see talking points below).
What to Say:
"Here's how we recommend thinking about the relationship. Start with a pilot. Four weeks. One client — ideally one of your existing accounts, not the 43,400-SKU client, not yet. We instrument proposal automation and alert triage for that account. You measure the time savings directly. Your strategist tells us what worked and what didn't. At week four, you have real data, not a vendor's pitch deck. If the pilot works — and we expect it to, but you should see it for yourself — we move to the full build-out. That's when we address the 43,400-SKU account, the translation pipeline, the cross-tool intelligence layer, and the KNAA bot concept. Now — you mentioned $100 million in 24 months. I want to be specific about why that number is relevant here, because it's not just about operational efficiency. When you sell a services business, buyers apply a multiple to EBITDA. For a manual agency with no tech, that multiple is typically 3-5x. For an agency with a documented AI system, proprietary data, and automated workflows, that multiple moves to 6-10x or higher. This is not speculation — it is the documented pattern in the Amazon agency M&A market right now. The technology you build with MERIDIAN is not an operating expense. It is enterprise value you are constructing every month. The 43,400-SKU client is not just revenue — it is proof of at-scale capability, which is what acquirers pay for. The next step we're proposing: a 48-hour proposal from us, scoped to the pilot. We pick one client from your current portfolio, define the measurement framework, and give you a concrete number for what the pilot costs and what it should save. No open-ended engagement, no scope creep. You either see the savings in four weeks or you don't proceed. Do you have a client in mind that would be the right pilot account?"
[Stop there. Let Carl respond. The question at the end is not rhetorical — it is the ask. If he names a client, the deal is advancing.]
"How is this different from Helium 10 or Jungle Scout at scale?"
"Helium 10 is a data retrieval tool — it tells you what is happening. MERIDIAN is an intelligence layer — it tells you what to do about it, remembers why you made each decision, and builds compounding context over time. The difference is the same as a spreadsheet vs. an analyst who's been working your account for two years."
"What happens if Claude's API goes down or gets expensive?"
"Fair question. The architecture is model-agnostic — the intelligence graph, the workflow layer, and the monitoring infrastructure all run independently of any single LLM. Claude is the reasoning engine today, but the data and workflows aren't locked to it. On cost: the hybrid model we're using (CLI + OAuth, not per-token API billing on basic operations) keeps costs predictable at scale."
"We tried something similar before and it didn't work. What's different?"
"Two questions: what specifically didn't work, and at what stage did it break down? Most failed AI implementations break at the integration point — the tool could do something impressive in isolation but couldn't connect to the real operational workflow. That's exactly what the pilot is designed to surface. We'd rather find the integration failure in week two than week twelve."
"What about data from my Tier 1 clients — can that leave our environment?"
"It stays in your subgraph. Your Tier 1 clients' data does not transit through any shared infrastructure. The Tier 1 agreement you have with Amazon is about your operational conduct on their platform — MERIDIAN processes your analysis data, not Amazon's proprietary data. That said, we'd encourage you to review the specific data types with your Amazon partner manager before the pilot. We can document exactly what data touches what system."
"How does the knowledge graph handle product catalog updates at 43,400 SKUs?"
"The graph schema is designed for high-cardinality product graphs. Each SKU is a node. Relationships carry edge-level metadata: price history, BSR trajectory, listing version history. At 43,400 nodes, graph traversal for alert triage is sub-second. The constraint is the ingestion pipeline — we'd want to understand the current data format (Seller Central reports? Custom exports?) before quoting a sync cadence."
"What's the latency on alert detection?"
"Depends on the monitoring cadence set per account. The architecture supports 15-minute polling for Criticals, hourly for High, 4-hour for Medium. Real-time is not economically justified at scale — a 15-minute detection window for a buy box loss is operationally equivalent to real-time for most intervention workflows. Your team can't respond in under 15 minutes anyway."
"How does the proposal generation handle Amazon category-specific nuances — grocery is different from electronics?"
"The generation pipeline uses category context as a top-level prompt parameter. The model is instructed to apply category-specific rules: grocery compliance flags, electronics hazmat considerations, etc. It doesn't hallucinate category rules — it references a structured category context library. That library is something we'd build with your strategists in the pilot phase, using their category expertise. The AI drafts; your strategists encode the rules."
"Who has access to our client data inside MERIDIAN?"
"The access model is: Alexander Mazzei and Ely Beckman (the MERIDIAN principals) have admin-level access during the build period. After production handoff, access is scoped to the operational account. You get an audit log of every access event. If you want a formal data processing agreement before the pilot, we can provide one."
"Can we self-host this eventually?"
"Yes. The architecture is designed for federated deployment — your node of the mesh can run on your own infrastructure. Timeline and cost depend on how deep into the build we are, but it's a documented migration path, not a theoretical one. We'd recommend staying on managed infrastructure for the pilot and first 6 months, then evaluating."
"What's the model for listing optimization — is it trained on Amazon-specific data?"
"The base models (Claude Haiku/Sonnet) have broad training that includes e-commerce and Amazon-adjacent content. The optimization happens at the prompt layer: structured prompts that encode A9/A10 ranking signals, character limits, keyword density targets, and backend field rules. It's not fine-tuned on Amazon data — fine-tuning is expensive and degrades quickly as Amazon's algorithm evolves. Prompt engineering is more maintainable and faster to update when Amazon changes the rules. Which they will."
"I want to see a live run, not a mock."
[If you have a live environment ready:] "Sure — give us an ASIN and we'll run the listing pipeline against it now." [If you don't:] "We intentionally used mock data today so you could see the structure without any client confidentiality questions. If you want a live run on one of your accounts, we can do that in a follow-up session — bring an ASIN you're currently optimizing."
"Another agency offered us something similar for less."
"I'd encourage you to ask them two specific questions: What does the data architecture look like, and do you own the trained model or just access it? Most tools offer AI features — very few offer a persistent knowledge graph that builds compounding value over time. The difference matters at exit. Ask them how the system affects your valuation multiple."
"We're not ready to move on this until Q3."
"Understood. Two things: the pilot is small enough that it doesn't require a major organizational commitment — one strategist, four weeks. And the 43,400-SKU client — is that account already live, or is onboarding happening in Q3? If it's live, the monitoring infrastructure is time-sensitive. The longer a 1,000+ SKU account runs without automated alert triage, the more operational risk is accumulating."
Used when: Carl is running late, strategists aren't on yet, or he opens with "I only have 30 minutes today."
Cut Acts 3 and 4. Compress Acts 2 and 5.
| Minutes | Content |
|---|---|
| 0:00–5:00 | Act 1 compressed — Open on knowledge graph. 90 seconds on the graph, 90 seconds on what we extracted from the call. Skip the digital audit entirely. |
| 5:00–17:00 | Act 2 — headliner only — Proposal automation in full (7 min). Alert triage in full (5 min). Skip content pipeline and cross-tool intelligence with this note: "We have two more pain points we'd cover in a full session — flagging for follow-up." |
| 17:00–22:00 | Act 4 condensed — Data ownership in 3 bullets. Do not show the architecture diagram. Say: "Your data stays in your subgraph, you get a full export at any time, we can walk through the full security architecture in a follow-up." |
| 22:00–30:00 | Act 5 full — Pilot offer, valuation multiplier story, the question: "Do you have a client in mind?" |
Do not apologize for cutting the demo. Say: "We've built a full 60-minute session — let's make sure you see the two things that are most relevant to where you are right now."
| Clock | Act | Milestone |
|---|---|---|
| 0:00 | Start — brief framing, no slides | |
| 2:00 | Open knowledge graph | |
| 7:00 | Transition to Act 2 | |
| 10:00 | Proposal automation | Carl should ask a question here |
| 16:00 | Cross-tool intelligence | |
| 20:00 | Alert triage | |
| 25:00 | Content pipeline | |
| 28:00 | Transition to Act 3 | |
| 30:00 | Carl Bot concept | |
| 40:00 | Act 4 — Architecture & Trust | Carl's specific questions answered |
| 50:00 | Act 5 — Deal Shape | |
| 55:00 | Ask the pilot client question | |
| 57:00 | Confirm next step (48-hr proposal) | |
| 60:00 | Close |
Watch for: If Carl starts asking deep questions in Act 2, let it run — that is signal that the pain is real. Compress Act 3 (Carl Bot) if needed. Never compress Act 5.
Within 2 hours:
Within 48 hours:
If Carl says yes to the pilot:
Full audit package: audits/prospect-audits/rankonamazon/ (8 files)
Social Media Presence
Social links on website: ZERO — no social media icons or links anywhere on the site.