Navira AI Listing-Optimization Platform

Where Navira is today

The current system is a no-code automation (Zapier, Airtable, Asana, Claude, Google Docs). It works for content, but the logic (prompts, the prohibited-keyword list, character limits) is buried inside the automation steps. Changing any of it takes a Zapier specialist who knows this specific build, which is the whole reason staff can't adjust anything themselves. There are no retries, so a failed AI call can silently push blank content into review. Per-task fees scale with volume, and creative was an unreliable bolt-on.

Current architecture

flowchart TD
    F["Airtable intake form"] --> Z["Zapier · 5 Zaps
logic buried in steps"]
    Z --> NVR["NVR API to Snowflake"]
    Z --> DD["DataDive"]
    Z --> CL["Claude"]
    Z --> AT["Airtable data"]
    Z --> AS["Asana review"]
    AS --> GD["Google Doc"]
    GD --> NB["Creative: Nano Banana
unreliable"]
      

The last four months weren't wasted. They're the head start

The current Zapier / Airtable build did its most important job: it proved the concept and produced a complete, working specification of exactly what Navira's listing engine needs to do. The new platform isn't a blank page. It's a re-implementation of a proven, fully-mapped system, and the requirements are already written, by something that actually ran.

What the prototype already gave us, and we carry forward

• The full content logic. Generation prompts, the 8-section content spec, and per-marketplace character limits (including Amazon's new 75-char title), with the correction step that keeps output in range.
• The compliance rules. The 80+-term prohibited list (6 categories) and brand blacklist, already defined and proven in production.
• The keyword pipeline. DataDive integration, ranked-keyword filtering, and the valued "Keyword Pull Only" mode.
• The workflow. The staged review and approval gates, and the multi-version (shared-output) logic for variations.
• The creative brief. The 6-infographic callout structure that now feeds the new templating pipeline.
• The data and integrations. The NVR API and Snowflake catalog, the intake fields, and the output format.

None of this has to be rediscovered. We're not writing requirements from scratch. We're rebuilding a known system the right way.

It also showed us exactly what to fix

Every weakness the prototype surfaced becomes a design requirement in the platform:

Why continuing on Zapier & Airtable would now hold Navira back

• It's the source of the #1 pain. The logic is locked inside the automation, so nothing is staff-editable without a Zapier specialist.
• Reliability ceiling. No retries and silent failures put content quality at risk.
• Cost scales the wrong way. Per-task fees grow with every listing and every step.
• It can't host the new value. The creative pipeline and deeper intelligence hit Zapier's ceiling (the creative struggles were partly that ceiling).
• It's rented, not owned. Accounts sit outside Navira, and every month spent extending it deepens lock-in we'd later pay to migrate off.

The recommended build: a Navira-owned application

We recommend starting small and proving the creative in-house before any larger commitment. Step one is a Proof of Concept. If it passes your test, we build the full owned platform around it.

If the concept passes, we build the rest of the system

One unified web app (tabbed: Intake · Admin/Config · Status) runs the show, with the admin dashboard hand-in-hand with intake so it reads as part of the product. Orchestration runs on owned code, catalog and state live in Navira's internal Snowflake platform, and the only outside services are the keyword engine, the AI models, and the review/output tools, each thin and swappable.

Target architecture

flowchart TD
    USER["Navira team"] --> UI
    subgraph APP["Navira-owned application"]
      UI["Unified web app, tabbed
Intake | Admin/Config | Status"]
      ORCH["Orchestration"]
      ENG["Content engine
Claude / OpenAI"]
      INT["Review intel +
competitor analysis"]
      CRE["Creative pipeline"]
      UI --> ORCH
      UI -. config .-> ENG
      UI -. brand kit .-> CRE
      ORCH --> ENG
      ORCH --> INT
      INT --> ENG
      ENG --> CRE
    end
    subgraph NAV["Navira internal data platform"]
      NVRAPI["NVR API"] --- SF[("Snowflake
catalog + state")]
    end
    DDV["DataDive · keywords"]
    ASA["Asana · review + design handoff"]
    OUT["Listing copy + creative + Google Doc"]
    NVRAPI -. catalog .-> ENG
    DDV -. keywords .-> ENG
    ENG --> ASA
    CRE --> ASA
    ASA --> OUT
      

The full path, with the gate up front

flowchart LR
    POC["Proof of Concept
creative concept"] --> GATE{"You decide:
proceed?"}
    GATE -->|yes| P0["Phase 0
own accounts +
app skeleton"]
    GATE -->|no| STOP["Stop here
only the PoC spent"]
    P0 --> P1["Phase 1
intake + admin app
+ content engine"]
    P1 --> P2["Phase 2
review intel +
competitor analysis"]
    P2 --> P3["Phase 3
creative pipeline +
localization"]
      

Because the current build isn't in active production, this is a clean build that reuses our existing platform stack, not a risky migration off a live system.

What's in each phase (preliminary)

Our current thinking on the work inside each phase. It's preliminary and firms into fixed not-to-exceed caps at detailed scoping, but it shows the build is costed from the actual work, not a round number. (Adjust the assumptions yourself on the Costs tab.)

At $100/hour, the full recommended path (Proof of Concept + Phases 0–3) totals 319–598 hours (~$32k–60k). It starts with the Proof of Concept (15–30 hrs, $1.5k–3k), a gated go/no-go that credits toward the build; the Phase 0–1 foundation that follows is 124–238 hours (~$12.4k–23.8k).

Creative & the templating layer

This is the piece that makes owning creative work. AI image models are great at pictures and unreliable at precise text: they garble words and drift off-brand. So we never ask the AI to render text. Every infographic is split into two layers:

1. Imagery (AI): backgrounds, lifestyle scenes, product-in-context. That's what AI does well.
2. Text + brand (template): headline, bullets, logo, colors, layout, rendered programmatically with pixel precision.

flowchart LR
    B["Infographic brief
from content engine"] --> AI["AI imagery
Nano Banana Pro / GPT image"]
    BK["Brand kit
fonts / colors / logo"] --> TMPL
    AI --> TMPL["Templating layer
composites text + brand"]
    TMPL --> QA["QA check
text accuracy + compliance"]
    QA --> ASA["Asana design handoff
human approval"]
      

How the template works

A template is an HTML/CSS layout with empty slots (background, headline, bullets, logo) styled by the brand kit (fonts, colors, logo set once per brand in the admin dashboard). The engine fills the slots with the exact callout text and the AI background, then a headless browser renders it to a PNG at Amazon's exact dimensions. The text is real type, not AI-drawn pixels, always spelling-perfect and on-brand. All six infographics share the brand styling, so the set is structurally consistent, not consistent by luck.

See it before you commit: a standalone creative concept

Your team already likes what Scalable produces, so the fair question is simply whether we can match that bar in-house. The low-risk way to answer it: we build a standalone creative concept first, a real sample set (main image plus infographics) for one of your live products, on the same approach we'd automate. You see the actual quality before committing to anything else.

• If you love it, we build the full platform around a creative engine you've already approved.
• If you don't, you've risked a fraction of a single month's Scalable bill, not the full project, and Scalable stays available as a fallback.

The concept is a small standalone engagement (about 15–30 hours, $1.5k–3k) and credits toward the build if you proceed.

What the research found

The "just buy Scalable" question

Scalable is a strong creative-first SaaS, and we took the buy option seriously. It markets full listings, voice-of-customer, competitor analysis, localization, and creative, which is broad coverage. But it doesn't fit Navira's core needs: no way for staff to edit rules (only brand-voice presets), no API into Navira's catalog or workflow, no staged approval, and your data lives inside its platform.

Its creative isn't proprietary

Scalable generates images on the same commodity models available to everyone (Nano Banana Pro and GPT image), which Navira already licenses through Google, OpenAI, and Anthropic. The differentiator is the templating/brand layer, which we build once and Navira owns.

And at Navira's volume, renting is expensive

At $35 per listing for ~100 listings/month, creative runs ~$3,500/month (~$42,000/year), every year. That $35 is a list rate, not a quote, so the real number could come in lower. Even so, the same output in-house, on the same models, costs a few hundred dollars a month. At the best published rate (~$24/listing) or a 50% enterprise discount, owning still wins by a wide margin.

Costs & investment

You commit to this one step at a time, starting small. Here's the staged path; the long-run economics (owning vs renting) are further down.

Phased investment (recommended Build path)

$100/hour, invoiced at milestones, not-to-exceed cap per phase. The build starts with a Proof of Concept, a gated go/no-go: if the creative concept lands you proceed, if not you stop, and the PoC credits toward the build.

The long-run picture: owning vs renting

Over 3–5 years, owning is dramatically cheaper than renting creative at $35/listing. The big numbers below are mostly the renting paths (Buy and Hybrid); owning lands far lower. This is a live calculator — change any assumption and the totals, chart, and tables update.

5-year cumulative cost. Build = own everything incl. in-house creative · Buy = Scalable wholesale · Hybrid = own the core, rent Scalable creative.

Monthly operating costs (edit any cell)

Exactly what goes into each option. The Scalable row is driven by the inputs above; every other cell is editable, so you can add Zapier, Airtable, a database, extra API fees, etc.

One-time build

Next steps

1. Start with a standalone creative concept. We build a real sample set for one of your products so you can see the in-house quality firsthand, before committing to anything further.
2. If the concept lands, confirm phase scope and set the Phase 0–1 not-to-exceed cap.
3. Begin Phase 0: ownership transfer and foundation mapping.

Leading with the concept means you only commit to the full build once you've seen the creative work for yourself. The risk on the first step is a fraction of a single month's Scalable bill.

What we'd need to start the concept

• A brand kit (fonts, colors, logo).
• One or two live products to build the sample set around.

For the full build that follows: access to coordinate the account/ownership transfer, and a quick confirmation from Justin on the Snowflake/NVR data integration.

Evan Foster · Evans List · hello@evanslist.tech