--- name: build-the-interface description: Build the Grokbot GTM interface from scratch for your own business. One static page with a left menu, a city map home and one view per GTM job, filled from JSON files by a small build script. Use when someone says "build me the GTM interface", "make the GTM map for my company" or "rebuild the interface from scratch". --- # Build the Grokbot GTM interface You are building one static web page that shows a company's whole go to market engine. It opens from disk, needs no server and no login. The data lives in JSON files. A build script turns the files into `index.html`. The sample in this folder (Tallyfern, invented) is the reference. When in doubt, copy what it does. The rule above every other rule. Nothing sends, posts or spends without a yes. The page only shows drafts. Before any paid data call, say what it does, how many calls and the most it can cost, then wait. ## 1. Interview first Ask one question at a time. Company name and site. What it sells and the price. Up to 3 customer segments. The job titles for payer, champion, user and blocker. 3 to 13 competitors. Channels used today. A first list of dream accounts, or permission to find them. Read the answers back and get a yes before building. ## 2. Files ``` index.html the page, written by the build build/build.py reads data/*.json, writes index.html build/style.css all styles build/app.js menu, router, tooltips, city map motion build/city.tpl.html the city map drawing with {{placeholders}} for every label build/icons.json line icons for the menu data/*.json everything the page shows ``` Build command, run from the folder. ``` python3 build/build.py ``` Python 3.8 or newer, no packages. Rebuild after every data change. ## 3. Menu and views Left menu with groups that fold open. The group of the open view stays open. Each link can carry a small count on the right. A top bar shows the view title and its group. On a phone the menu slides in from a button. | Group | View | Hash | What it shows | |---|---|---|---| | (top) | City | `#overview` | The city map, the engine in order, city in numbers | | Daily rhythm | Morning brief | `#brief` | Meetings to prep today and the focus list | | Daily rhythm | Reply inbox | `#inbox` | Replies grouped by what they need, one drafted answer per group | | Daily rhythm | Slack alerts | `#alerts` | High signals as a Slack preview, marked "Preview, Slack not connected" | | Daily rhythm | Weekly report | `#weekly` | The Friday numbers and one change for next week | | Engine | CRM | `#crm` | Its own second menu, see below | | Get customers | Target accounts | `#targets` | Account cards with fit out of 100 and the buying committee | | Get customers | LinkedIn campaign | `#campaign` | The sequence by day, marked "Draft, not sent" | | Get customers | ABM | `#abm` | One angle, asset and channel per committee member | | Get customers | Signal engine | `#signals` | Signals ranked by score with a next action | | Organic social | Format finder | `#formats` | Post formats that work and how you make each one | | Organic social | Content calendar | `#calendar` | 30 days of posts, each "Draft, not posted" | | Search | SEO | `#seo` | Keyword gaps with volume, cost per click and ranks | | Search | GEO | `#geo` | Unbranded AI prompts and whether you are named | | Search | Programmatic pages | `#pages` | Pages proposed from the gaps, a written one opens as a full draft view (`#pg-draft` in the sample) with a back link | | Market | Competitive analysis | `#competitive` | Rivals by threat, traffic, pricing, moves, ads, news | | Market | Battlecards | `#battle` | They say, we say, the question to ask | | Under the hood | Guardrails | `#guard` | The rules the agent follows | | Under the hood | Data providers | `#hood` | One key, several data providers. Runs grouped by provider with calls, cost, how many answers feed the page and every miss | | Under the hood | Run log and cost | `#runlog` | Every paid run with calls and cost | | Under the hood | Next to plug in | `#next` | Connections not built yet | CRM second menu. Overview (key numbers, pipeline by stage, numbers by list), Pipeline board (one column per stage, cards open the record), People (filters for list, stage and name, 100 rows then "Show 100 more"), Companies, Lists, Replied, Awaiting reply, Meetings, Trials and paying, Activity timeline, Tasks, Reports (funnel per list), Schema. Clicking any person opens a record drawer on the right with the stage bar, details, blurred email and the next step. ## 4. Look - White paper background, white cards with a thin grey border and 12px corners, soft shadow. - One accent colour, set once as `--ember` at the top of `style.css`. The sample uses blue. Swap it for your brand colour (pink works) and every bar, focus ring and link follows. - Inter for text, Roboto Mono for numbers and table headers. 16px body text, 8px spacing grid. - Every view starts with a small group label, the title with an info button (hover shows what the view is) and a row of pills. - Pills say the state in plain words. Green for "Nothing on this page sends anything", amber for "Draft, not sent", "Draft, not posted" and "Draft, not published", grey for "Sample data" and counts. - Numbers sit in key cards (label, big number, unit, one line underneath). Lists sit in tables inside a bordered box that scrolls sideways on a phone. - People and companies show initials in a round or rounded square badge. No photos by default. - The home is an isometric city on a dark navy board. Engine quarter on top (CRM HQ, Daily rhythm tower, Signal engine dish, Campaign lanes, Format studio, Programmatic pages, Run log meter, Guardrails gate). Market quarter below (rival towers, taller means more visits, roof colour means threat; buyer houses coloured by segment; funding coins; ad billboards; news stand; search plaza with AI answer share). Every building is a link with a tooltip that reads the same number as its view. Keep the drawing in `city.tpl.html` and fill labels at build time, so the map never drifts from the data. ## 5. Data files and fields | File | Fields | |---|---| | `company.json` | name, domain, tagline, offer, price, currency, built, sample_note, segments (key, name, legend), icp, channels | | `accounts.json` | tracked_total, accounts (id, name, domain, segment, industry, country, staff, fit, fit_parts (icp, committee, signal, activity, email), why, committee (role, name, title, email, note)) | | `signals.json` | signals (account, type, score, what, date, action) | | `crm.json` | stages, lists (id, name, segment), mrr_per_paying, people (id, name, list, segment, stage, title, last_touch, email), tasks (what, due) | | `campaign.json` | name, status, steps (day, channel, kind, text), sent_14d, lists_live | | `abm.json` | accounts (account, plays (role, angle, asset, channel)) | | `content.json` | formats (name, what, how_we_use_it, fit), calendar (date, channel, format, hook, status) | | `competitors.json` | rivals (rank, name, domain, threat, visits_k, pricing, positioning, recent_move, ads, funding_musd), news (date, title, rival), activity (posts_90d, changes_90d), battlecards (rival, they_say, we_say, ask) | | `search.json` | keyword_gaps (keyword, volume, cpc_eur, rival_rank, our_rank), geo_prompts (prompt, top_named, we_are_named), pages (slug, title, keyword, status), draft (slug, title, lead, sections) | | `daily.json` | brief (date, meetings (time, account, who, prep), focus), inbox (group, count, draft), alerts (time, text), weekly (week, lines, note) | | `runlog.json` | runs (date, what, calls, cost_usd, job, provider, hits, misses), misses (date, job, provider, input, why, cost_usd), provider_notes (provider name to one line on what it does), guardrails (rule, detail), next (what, detail) | Accounts link to signals, ABM and meetings by `id`. Roles are always payer, champion, user and blocker. A role nobody holds yet keeps `name` empty and a `note` such as "not found yet". ## 6. How each view reads its data - City and city in numbers. Counts from every file. CRM totals come from `crm.json` people by stage, reply rate is replied over contacted. - Morning brief, Reply inbox, Slack alerts, Weekly report. `daily.json`, meetings join `accounts.json` by id. - CRM. `crm.json` for people, lists, stages and tasks. Companies come from `accounts.json` plus `tracked_total`. - Target accounts. `accounts.json`, sorted by fit, with the top signal per account from `signals.json`. Fit parts show on hover. Display names are first name plus last initial. - LinkedIn campaign. `campaign.json`. - ABM. `abm.json` joined to `accounts.json`. Only accounts with 3 or more roles named. - Signal engine. `signals.json` joined to `accounts.json`, sorted by score. - Format finder and Content calendar. `content.json`. - Competitive analysis and Battlecards. `competitors.json`. - SEO, GEO, Programmatic pages and the draft page. `search.json`. - Guardrails, Run log and cost, Next to plug in. `runlog.json`. - Data providers. `runlog.json`. It groups `runs` by `provider` and adds up calls, cost, hits and misses per provider. A provider with hits shows how many answers feed the page. One with none shows tried, not used. The table lists every row in `misses` with the reason. A miss costs nothing and stays in the log so the cost line adds up. The provider names in the sample are invented. ## 7. Blur by default - Every email and every piece of message text gets the class `blur` (a 4.5px blur, text not selectable). - A switch at the bottom of the menu reads "Private data blurred". Pressing it adds `unblur` to the body on that screen only and says "Private data visible". It always starts blurred. - No photos by default. Show initials. If someone adds photos later, keep them local files and blurred until the switch is off. - Never print a full name in a card or table. First name plus last initial. ## 8. Fill each view with the matching pack skill Each view has a skill in the Grokbot GTM pack (https://www.heyarnoux.com/grokbot-gtm/) that produces its data. Run them one by one, write the result into the matching JSON file in the fields above, then rebuild. | Pack file | Fills | Data file | |---|---|---| | `skills/icp-scoring.md`, `skills/target-accounts.md`, `skills/account-scan.md` | Target accounts, CRM companies, fit | `accounts.json` | | `skills/buying-committee.md`, `skills/prospect-list.md`, `skills/crm-scan.md` | Buying committees, CRM people and lists | `accounts.json`, `crm.json` | | `skills/signal-radar.md`, `skills/account-alerts.md` | Signal engine, Slack alerts | `signals.json`, `daily.json` | | `skills/abm-plays.md` | ABM plays | `abm.json` | | `skills/linkedin-campaign.md`, `skills/outbound-drafts.md` | LinkedIn campaign | `campaign.json` | | `skills/format-finder.md`, `skills/content-calendar.md` | Format finder, Content calendar | `content.json` | | `skills/competitive-analysis.md`, `skills/competitor-monitor.md` | Competitive analysis, Battlecards, map market quarter | `competitors.json` | | `skills/seo-check.md`, `skills/geo-check.md`, `skills/programmatic-pages.md` | SEO, GEO, Programmatic pages | `search.json` | | `routines/morning-brief.md`, `skills/meeting-prep.md`, `skills/reply-sorter.md`, `skills/weekly-report.md` | Morning brief, Reply inbox, Weekly report | `daily.json` | | `skills/guardrails.md` | Guardrails, Run log and cost, Data providers | `runlog.json` | Every path above sits under https://www.heyarnoux.com/grokbot-gtm/ and in the pack zip. Each paid run adds one line to `runlog.json` with its date, calls, cost, provider, hits and misses. Each miss also adds one line to `misses`. Before it runs, show the price and wait for a yes. ## 9. Before you call it done - Run the build, open the page, click every menu link and every CRM tab. No errors in the browser console. - Check the page at phone width. No sideways scroll. - Search the folder for any real email, photo link or private note that should not be there. - Remove generator tags and tool comments from the HTML. Strip metadata from any image. - Every send and post is still a draft waiting for a yes.