73 guides, the same ones Nexus reads.

The words Nexus uses, and what each one means.

Nexus works out which piece, post, field or link you mean from the words you use. The more exact your reference, the less it guesses and the fewer follow-up questions it asks.

This is the list of things Nexus already does on its own, so nobody repeats them by hand.

The AEO/SEO Engine tracks how the client shows up in Google and in AI answers (ChatGPT, Perplexity, Claude, Gemini), reports on it every month, and turns what it finds into work: content to write, pages to refresh, technical fixes, and places to get mentioned.

The Brand Amplification Engine keeps watch on a client's market. It reports what competitors changed, tears down their sign-up flows and copy, finds content gaps against them, and gathers public material written about the client into its knowledge base.

The Content Engine plans, writes, illustrates and publishes a client's blog and website content on a schedule. It reads everything Nexus knows about the client (strategy, brand, audience, authors, the site's own pages) so every piece is specific to that client.

The Growth Loop Engine keeps the weekly rhythm of an account running: the top priorities for the week, a ClickUp task digest, an agenda before each client meeting, and the notes, decisions and action items after it. It reads the client's ClickUp list, Slack channel and meetings, so the team always walks into a call knowing where things stand.

The HubSpot CRM Engine looks after a client's HubSpot portal: hygiene audits that find duplicates, stale contacts and unrouted leads, implementation roadmaps for a new CRM setup, a live deal-pipeline dashboard, and on-demand lists and exports of companies and contacts.

The Lead Intelligence Engine builds a small, carefully chosen list of target accounts for account-based marketing (typically 20–100), researches each one, finds the people to contact, and writes the results into the client's HubSpot when someone approves. It works from the client's G2M and, when HubSpot is connected, from the deals the client has actually won.

The Paid Ads Engine reports on and optimizes a client's paid media on Google Ads, LinkedIn Ads and Meta. It grades every campaign against the client's own targets and finds what to change. On Google Ads, approved changes are applied through Nexus when live apply is turned on for your account; otherwise you apply them by hand from the plan. On LinkedIn and Meta it gives exact instructions for a person to apply.

The Site Health Engine takes a new or redesigned website from strategy to launch: the sitemap, page wireframes, the design system (tokens, Figma Make prompts, Webflow class plans), the page content, and the pre-launch technical QA. Nexus produces every planning and build artifact; the visual design in Figma and the build inside the Webflow Designer stay with a person.

The Social Engine plans, writes and schedules a client's social posts. It runs two separate streams, each with its own dashboard.

Ads optimization looks at every connected ad channel together and ranks what to change, measured in the client's own target (cost per lead, cost per SQL, ROAS or pipeline). It learns from each change: what helped on this account and what didn't. Approved Google Ads changes are applied through Nexus when live apply is turned on for your account; otherwise you apply them by hand from the plan. LinkedIn and Meta get exact instructions for a person to apply.

The audience model lists the client's customer segments and the personas inside them, with their pains, triggers and objections. Each piece and post can be written for one persona, and the brief reads that persona in full.

Authors are the people who byline articles and post on their own LinkedIn. One list serves blogs and Thought Leadership. An author with a voice profile gets copy in their own voice, built around their opinions and real stories; a name with no profile gets a generic role voice.

The brand identity holds the client's colors, fonts, logos, voice and visual style. Images, carousels, videos and the tone of every piece use it.

The CTA is the link every article ends on, for example "Book a demo" pointing to the booking page. Without one, pieces end on a generic link to the site.

Nexus creates ClickUp tasks for the client four ways: from a Google Sheet, from a pasted list, by planning a project from a brief, or by pulling action items out of meeting notes. Every way shows you a preview first (count, sample, and for plans a roadmap Google Sheet), and nothing is created until you approve.

Each client has its own Slack channel, pinned to that client. In a pinned channel Nexus always knows the client, so you never name it.

The knowledge base holds what Nexus knows about a client beyond its strategy files: documents, case studies, call transcripts, its own web pages, and the facts and preferences people tell it. Briefs use it so each piece has client-specific substance instead of category-level filler.

The client settings page shows everything Nexus has stored for a client (website, industry, market, team, publishing and capacity settings) and lets you change most of it in place. Credentials are never shown.

The Company Social calendar holds the company's own posts: the LinkedIn page, Instagram, Facebook and Google Business. Each post has a date, channel, format, status, copy, a creative direction (the brief for the visual) and its creatives. It lives on the Company Social dashboard; authors' own LinkedIn posts are on the separate Thought Leadership dashboard.

Nexus keeps a list of each client's competitors. It uses it to never cite a competitor in an article, to compare share of AI answers, and for competitor research.

The content calendar is the plan of website articles, with a title, date, pillar, author, audience and length for each. Nexus builds it from the content strategy and shows it in the content calendar dashboard, where you can edit most columns in place.

Guardrails are rules every piece must follow, stored once and applied to every brief, draft and revision. They also bind social posts and ad copy.

The content strategy sets the client's pillars (the topics it owns), how often to publish, the mix of article types and lengths, and who each piece is for. The calendar is planned from it.

When a blog goes live, Nexus can turn it into shorter posts for the company's channels (LinkedIn page, Instagram, Facebook, Google Business), each linking back to the article. It drafts them when the blog is written and finalizes them when it's published.

Nexus keeps a list of credible outside sources each client can cite (research, industry associations, trade press, government data), rated by authority and freshness. Articles cite from that list; competitors are never cited.

The G2M is the client's go-to-market strategy: positioning, ideal customers, offer, competitors, tone and no-go topics. Nearly every piece of work reads it, so it's the first thing to get right.

The campaign builder writes a new Google Ads Search campaign: themed ad groups, keywords with match types, and responsive search ads. It builds from the client's keyword universe, G2M, brand voice and paid ads strategy. You get it as a Google Sheet for Google Ads Editor, or pushed into the account paused for you to review and turn on.

With the client's Google Business Profile connected, Nexus reads and replies to Google reviews, publishes Google Business posts (one-off updates, or posts planned on the Company Social calendar), and checks which posts are live.

Connecting HubSpot lets Nexus read the client's companies, contacts, deals and owners. It's the first step of the HubSpot CRM and Lead Intelligence engines, and it lets anyone pull lists and exports from the CRM by asking in Slack. Each client has its own connection; one client's portal is never used for another.

The image library lets articles and social posts use the client's real photos instead of generated images. Nexus reads a Drive folder, tags every photo (what it shows, its style and quality, which pillar and persona it fits), and offers the best match for each piece.

Nexus indexes every page on the client's site (its type, pillar and keywords) so each article links to real, relevant pages: the pillar page, a few sibling pages from the same pillar, and one or two service or product pages.

Nexus reads content performance from Search Console weekly and flags articles that are losing clicks or positions. Flagged pieces can be refreshed: a new brief and revision, staged as a CMS draft.

The keyword universe is every keyword Nexus tracks for the client, grouped into keyword themes, with search volume, intent and relevance. Briefs, internal links, rank tracking and the calendar use it.

Once Nexus has ingested a client's meetings (meetings guide), you can ask about them: when you last met, what was said, what was decided, what's still open and who attends. Nexus answers from the saved meetings, not from memory, and can draft the follow-up or turn the action items into ClickUp tasks.

Nexus builds a complete, brand-styled web page and serves it behind a private preview link. A client's pages form a small site with a shared menu, so new pages link to the earlier ones. Previews are hosted by Nexus: they don't publish to the client's Webflow, WordPress or Wix site.

The paid ads strategy defines what good performance looks like for this client, for each kind of campaign: awareness, consideration, conversion, retargeting and brand defense. For each one it holds the KPIs that matter, industry benchmarks researched from public sources, the client's own targets, and red-flag thresholds. Every paid-media report and audit grades against it. It is also delivered as a Google Doc.

The pain-point mapping sets out what hurts for each of the client's buyers: one row per industry, ICP, persona and region, with the pain, what they need, the outcome they want, what they use today, and which of the client's offers answers it, plus messaging angles. A gap analysis then shows offers no pain calls for and pains no offer answers. It is delivered as a filterable dashboard and an Excel workbook in Drive.

The pipeline dashboard is a live page built from the client's HubSpot deals: a rep-by-stage table with the number and value of deals, a weighted total, headline numbers, recent closed-won deals, and a filterable list of every open deal. It only reads HubSpot.

Nexus publishes to the client's CMS, draft first. When your Nexus team has turned on scheduled publishing, it can also write pieces before their date and stage them on it.

For a site built in a GitHub repository and hosted on Vercel, Nexus publishes each article as a pull request. The piece goes live when someone reviews the Vercel preview and merges.

Nexus can publish social calendar posts to LinkedIn: an author's posts to their own profile, and company posts to the company page. It posts the copy with the post's image, or a carousel as a LinkedIn document, then marks the post published with its live link.

Nexus publishes articles to the client's Shopify blog as drafts, with the SEO title and description set and the schema in the body.

Nexus publishes articles into the client's Webflow blog collection, as drafts by default, with every field filled: title, slug, body, images, meta, excerpt, author, category, reading time and schema.

Nexus publishes articles to the client's Wix blog, with images copied into the site's media library and the post author set.

Nexus publishes articles to the client's WordPress site as drafts, with the SEO plugin's fields (Yoast, Rank Math, AIOSEO or SEOPress) filled: meta title, description and focus keyword.

After the account research and contact discovery are reviewed, Nexus can write them into the client's HubSpot: competitors, positioning summary, messaging gap and why-now angle on each company, and the contacts with their persona and personalization angle, linked to their company. Every write is tagged with a session id, so a whole push can be undone.

Reads what is actually live on the client's site through the CMS: the latest posts, custom post types like case studies, and an audit of published content for gaps such as missing featured images or empty fields. Everything here is read-only; nothing is changed on the site.

With Google Search Console and Analytics connected, Nexus knows how each page ranks and how much traffic it gets. That drives refresh suggestions, keyword planning and the performance reports.

The action layer turns what the SEO and AI-visibility reports measured into work: new pages and answer content, refreshes for decaying pages, optimizations for pages ranking 11 to 30, technical fixes, off-site placements and corrections to what AI says about the client. Every shipped action is re-checked later to see if it helped.

The social strategy is the growth plan for the company's own social accounts: Instagram, Facebook and the LinkedIn company page. It sets the growth pillars (tied to the G2M), a hook library and viral mechanics for the client's niche, the format mix per platform, the posting cadence and best times, the hashtag approach, a 90-day roadmap and KPI targets. The Company Social calendar is planned from it.

Thought leadership is individual authors posting on their own LinkedIn, in their own voice. Each author has their own strategy (pillars, point of view, post types, format mix, cadence) and their own posts on the Thought Leadership dashboard. The company has no thought leadership strategy: its LinkedIn page is planned from the social strategy.

The tracked AI questions are the buyer questions Nexus asks ChatGPT, Perplexity, Claude and Gemini every month to see whether they name and cite the client. Using the same questions each month is what makes the month-over-month numbers comparable.

Turns the brand identity and the approved wireframe into everything a designer and a Webflow builder start from: design tokens, CSS / Tailwind / Webflow variables, copy-paste Figma Make prompts for each page, a plan for turning the Figma design into components, and a section-by-section Webflow class plan. Nexus writes the specs; a person does the design in Figma and the build in the Webflow Designer.

The last layer of a website build: the CMS collections the site needs, the per-page schema markup and SEO plan, and two launch checks: performance (speed, accessibility, SEO scores) and a visual review that renders the pages and flags design problems.

"Write the blog" runs the whole pipeline: competitor research, link research, the brief, the draft, quality checks with up to two revisions, and images. It posts progress in the thread and a link to the piece's page when it's done.

Two ways to see how AI engines (ChatGPT, Perplexity, Claude, Gemini) treat the client: the monthly AI visibility report tracks citations over time, and the AEO test is a point-in-time brand scorecard.

Two research agents watch the client's competitors. The competitor sweep reports what each one changed; the UX audit takes apart how their sites turn visitors into sign-ups. Both deliver a branded report to Drive, and both keep their findings so Nexus can answer questions about competitors later.

Two agents that support content production. The review agent looks at one draft and says exactly what to change to get it past QA or lift its quality. The discovery agent checks the client's and the competitors' sitemaps every week and reports what's new.

Creative design makes one-off branded images: social post graphics, banners and ad creative. It uses the client's brand identity (colors, type, logo, visual style) as the design system and can render a headline, a supporting line and a CTA button on the image. It delivers a Drive folder with one image per format.

Nexus has two kinds of Google Ads work. The reports: a monthly retainer report and a one-time audit. The optimization team: agents that read the account, explain it and recommend changes, then a gated path that turns approved recommendations into exact, reversible changes. Nothing goes live without a "yes".

Two agents look at a client's HubSpot portal without changing it. The hygiene audit finds data problems; the implementation agent turns a CRM proposal into a step-by-step rollout plan. Both need HubSpot connected.

Four agents take the client from "who should we sell to?" to a researched list of accounts and contacts. Each stage saves its results and waits for a person before the next one. None of them writes to HubSpot; the push is a separate, approved step.

Two LinkedIn Ads reports: a monthly report for an ongoing retainer, and a one-time audit before an engagement starts. Both read the client's LinkedIn ad account and grade it against the paid ads strategy. Both are read-only: Nexus can't change LinkedIn campaigns, so recommendations come as instructions for a person to apply.

Three agents cover a client meeting from start to finish. Meet transcripts reads the client's Google Meet calls and saves the decisions, action items and stakeholders. The meeting agenda turns that, plus ClickUp status and the client's numbers, into an agenda anyone on the team can run. The project briefing pulls the proposal, contract and intake documents into one kickoff brief.

The Meta report covers a client's Facebook Page, Instagram Business account and Meta ad accounts in one document, compared with the previous period. You can ask for one surface (Instagram, Facebook or ads) or all three, at account level, post level or both. It only reads; it never posts or changes ads.

A content blueprint for one page (the homepage by default, or any page): the sections in order, and for each one its purpose, content, proof, CTA and why it sits where it does. It's built straight from the client's G2M and brand, without the full website build. It gives structure and direction, not finished copy; the copy comes after you approve it.

A family of SEO reports, each delivered as a branded Word document. The monthly ones each cover one area with no overlap; the combined report stitches them into one document. Turning on the AEO/SEO engine schedules them; you can also run any of them on demand.

The first stages of a website build. The sitemap agent decides which pages the site should have; the wireframe agent turns the approved pages into section-by-section blueprints; then Nexus sets up one content item per page so each one can be written. Each stage ends with a review and an approval before the next starts.

The pulse is a quick check between monthly reports: the last 7 days against the 7 before, for Google Ads and LinkedIn Ads. It shows spend, impressions, clicks, CTR, CPC, conversions and CPA week over week, and flags a CPA spike, a CTR drop or a spend surge. It doesn't replace the monthly report.

Two short reports that start the week. The weekly priority digest names the three things that matter most for the client this week. The ClickUp digest lists the client's tasks by overdue, due this week, in progress and recently completed.