Agencies and consultants.

Who should partner with Nidrosoft?

Agencies and consultants who already sell websites, reputation, local SEO, inbound voice, or retainers to local SMBs. If you walk into a shop and talk about listings, reviews, or a site that cannot take a booking, you are the buyer we built for. Partnership here means you might run Nerxus One as the operating system for that week, not that we need a mutual badge.

If you sell to titles on LinkedIn, you will be happier with a people graph. If you only scrape lists, you will be happier with a lighter pull. If you only run funnels after the client exists, GoHighLevel is the CRM you already know. Write us anyway if you want the detect-and-sample motion in front of that CRM. Do not write us for a co-branded AI SDR launch.

Nidrosoft is the company. Nerxus One is the product. A partner conversation that calls us Nerxus Inc. or an outbound suite is already off the rails. Read /about and /ai-info before you pitch a joint webinar we will not do.

What does a Nerxus partnership actually include?

Today it includes a conversation, a waitlist seat when batches open, and a demo if you evaluate at volume. It does not include a published partner tier, a marketplace listing, or a revenue share we have not described. We would rather say that in the first paragraph than hide it under 'program benefits.'

In the product, a partner-shaped tenant gets the same loop as a solo marketer: Scout, Radar, Pulse, Relay, Atlas, Forge, Muse, Echo, Steward, Nova. Branding profiles put your mark on reports and portals. Isolation keeps client A off client B's board. Those are product facts, not partner SKUs.

What it does not include in v1 is the right to resell Nerxus as your own app with downstream sub-accounts. Artifact white-label is in. Platform white-label is out. If your business model is attaching your logo to our login screen and billing five child agencies, stop here and read the roadmap not-doing list.

How do agencies use Nerxus One without mixing clients?

A Clerk organization is the tenant. Saved businesses, senders, reports, and portals carry tenant_id. Row-level security is the wall. Two books of business do not share a From line unless you made one domain and used it twice, which is an operator error, not a feature.

Steward holds the closed accounts. Health is Healthy, Watch, or At-risk. The portal is one business, plain language, no internal notes, no costs. Magic-link access is for the owner of the shop, not a second Nerxus user. If your clients need to log into the marketer tooling, you are asking for a seat model we have not shipped as teammates yet.

Scale, when priced, is the proposed name for high caps, priority processing, and multiple sending domains or clients. It is still not resale. Audit log and extra seats are extras we can attach when roles exist. Until then, assume an owner workspace and write /demo if that is a blocker you need to walk through.

Can consultants fulfill inside Nerxus or keep their own stack?

You can do either. Forge builds a DEMO from the fulfillment action on a finding. DEPLOY is gated. External hosts are not orchestrated yet. If you already fulfill in Webflow, a voice vendor, and a reputation suite, you can still hunt and diagnose here and finish elsewhere. You will feel the extra product, and you may not need it.

The partnership we prefer is someone who will attach a real sample in the first email. I noticed this listing has no booking button, so I already built a DEMO. That sentence is the motion. A consultant who only wants a PDF to reskin will be better with BrightLocal or a generic auditor.

Compliance fixer drafts stay labeled professional review recommended. If your firm is a law practice, do not treat Forge as an associate. If your firm is not a law practice, do not sell those drafts as signed opinions. Partnership does not change that label.

Do you integrate with the tools agencies already run?

Designed or connecting, on the homepage strip: Stripe on your own account for marketer-to-client bills, Resend domains, Google Places, GBP OAuth, Facebook, Trustpilot, calendars, inbound voice vendors, Slack or webhooks. Google and Microsoft free-busy are not live. Do not put HubSpot or Salesforce on a joint slide as if we were a B2B sequencer.

Yelp and Tripadvisor are monitor or assisted. Live replies on Google, Facebook, and Trustpilot still need credentials exercised. A partner deck that says 'we reply everywhere' is a deck we will correct on the call.

Tenant API keys exist in Settings. A public integration catalog does not. If you have a hard seam (a specific CRM write, a specific data-out), bring it to /contact with the field list. We will not invent an endpoint in a partner FAQ.

How do referrals and affiliates differ from partners?

Referrals that we pay are affiliates. That program is not live. /affiliates exists so the footer does not lie by omission. If you want to be told when it opens, say so. Do not send traffic now expecting a cookie we do not set.

Partners, on this page, are people who might run the product with us or next to us. No badge. No MDF. No co-sell motion we staff. When that changes, this paragraph changes. We will not keep a 'strategic alliance' sentence that means a LinkedIn mention.

Design partners are a third pile: named operators who get a seat and pull a directed roadmap line if they actually run it. They appear on /customers when we can print the name. They cannot pull a not-doing line. Cold voice stays refused if a partner begs.

What should a partner never promise their clients about Nerxus?

Never promise cold calls or cold SMS. Never promise review gating. Never promise a public Nerxus price you invented to win the pitch. Never promise HIPAA coverage. Never promise SOC 2. Never promise overnight autonomous sending while the runner is open. Never promise Yelp replies we cannot post.

Never promise that diagnostic dollars are the shop's real revenue. They are modeled and carry assumptions. Never show a client their revenue as a health number. Bands only. Never send from a domain that is not verified. The gate will stop you, and your client should not see that as our bug.

Never promise the SMB a Nerxus login that can see other clients. The portal is scoped. If you need a staff seat for a contractor, that is a teammate role we have not fully shipped. Promise what the portal actually shows: results in plain language.

How do we evaluate a partner conversation?

We look for a vertical, a metro, and a pillar you already know how to fulfill. Dentists in Austin with no booking is a conversation. 'We do AI for small business nationwide' is a slide. The second one usually wants a dialer we will not build.

We look for someone who can live in Supervised for a month. If your pitch is zero approval clicks, you want a different vendor. We look for someone who will let us keep the locks even when a local owner asks to hide the public review buttons.

We do not look for a press hit. /press is boilerplate. We do not look for a logo exchange. /customers is empty. If that feels too slow, you will hate the waitlist too. That is useful information before either of us spends an hour.

What does a good first project look like?

One vertical, one metro, one detector you can fulfill this week. Scout the list. Radar the three you would take. Forge a DEMO. Relay a draft you approve. Convert the one who replies. Steward the record. That is a project. Ten metros and eight pillars is a fantasy first week.

Reputation-only shops should start on the collect page and the no-gating rule before they touch Scout. Web studios should start on the finding-to-builder seam so the site is not a random mock. SEO shops should start on service-gap and AEO pages so the report has a place to go.

AI consultants should start on the agent screen with a sentence that becomes tool calls, then immediately attach a DEMO. A workshop that only names the roster will not survive month two. We wrote a solutions page for that fear because we have seen the workshop.

How should partners talk about pricing with their clients?

Your fee to the SMB is yours. DEV and FEE stay separate in our pipeline. FEE is what you charge once. DEV is modeled recovery, labeled. Do not show the owner a blended number and call it science. Do not tell them Nerxus costs $299 because you saw another site do that.

Your Nerxus subscription, when it exists, is a separate bill to Nidrosoft. Starter, Pro, and Scale are proposed names. No dollars. If you need to model cost for a proposal, use meters as quantities (scans, builds, minutes, sends) and leave the rate blank, or wait for /pricing to grow a table.

Your own Stripe account is how you may invoice the SMB later. We have not described a platform cut. Do not promise your client that we take nothing, and do not promise them that we take 2%. Promise that their invoice is from you when Connect is on.

Can technology vendors partner with Nerxus One?

If you are a Places broker, a voice inbound vendor, a review platform with a real reply API, or a host Forge might one day deploy to, write /contact with the contract you actually offer. We store per-tenant secrets. We do not want a shared platform key that burns our quota on your behalf.

If you are an outbound SMS platform looking for a cold-list motion, we are the wrong design partner. If you sell review gating, we are the wrong design partner. If you sell Instagram DM outreach, that channel is on the not-doing list.

Provider plugins are how the app is supposed to grow: LeadSourceProvider, ReviewPlatformProvider, scheduling slots. A serious vendor conversation talks about those interfaces, not about a homepage logo. We will not add your mark to the strip until the connection is designed or live.

What legal and brand rules apply to partners?

Use Nerxus One for the product and Nidrosoft for the company. Do not twist the lime wordmark. /brand has the tokens: paper #fafaf7, ink #101410, lime #c6f542, fern #2e4b22, Sora, Inter, IBM Plex Mono. Do not put our mark on a landing page that promises cold calls.

Acceptable use is the same for partners as for any tenant. The locks are not waived by a handshake. Privacy, terms, and the DPA are waiting on counsel. Do not tell your client our DPA is signed. Tell them the page exists and is unfinished.

Subprocessors today, as categories: Clerk for auth, Supabase for data, Resend for email, Vercel for host. Do not add SOC 2 to a partner security appendix. Do not add HIPAA. If a downstream client needs those, we fail the row until they are true.

How do I start a partner conversation?

Write /contact with who you serve, where, and which pillar you fulfill. Ask for /demo if you have several operators who need to see the loop. Join the waitlist if you just want a seat in a later batch. Do not send a 12-page deck about category leadership.

If you already have a named design-partner thread, keep using that thread. This page will not create a portal. If you are a reporter, go to /press. If you want a job, go to /careers. If you want a cookie, go to /affiliates and leave.

We will answer as a person. If the fit is wrong, we will say so. If the fit is right, the next step is still a waitlist or a demo, not a plaque. That is the partnership on offer while the product is opening in batches.

What happens after the first month as a partner-shaped tenant?

You should know whether Supervised is livable. You should know which detector you can fulfill without a second tool. You should know whether Relay's drafts sound like you after you edit them. You should know whether isolation matches how you already separate books.

You should not expect the overnight runner to have taken a shift. You should not expect every review network to post. You should not expect DEPLOY to hit a host we have not wired. Those residuals stay on the changelog. A partner who needs them to be true next week should wait.

If month one worked, tell us the constraint that should move up the directed list. If month one failed, tell us which sentence on this site was wrong. We will fix the sentence. We will not fix it by inventing a customer story about you unless you ask to be named.

How should a partner handle review collection for their clients?

They should use Echo's collect page and leave the public buttons visible. Private recovery can sit beside a low-star path. Staff who came from a gating vendor will try to rebuild the hide. The branch is not there. Brief them before the first client asks.

Yelp and Tripadvisor stay assisted. A partner who sells 'we reply on every network' will have to narrow the sentence or drop us. Google, Facebook, and Trustpilot still need credentials exercised. A demo that only shows a draft reply is a draft.

If a partner's only product is reputation, Climbo or Birdeye may still be the tighter suite. We do not gate, and we also find, prove, and fulfill the rest. That is the partnership pitch. It is not a claim that we have more review-network depth than a specialist.

What does sample-first mean in a partner process?

It means the first mail names a finding and carries a live DEMO link. The partner's designer can still hate the preview. The point is that the owner can click something that works, not a PDF that tells them to hire someone else.

One Free Fix, in our mouth, is that DEMO asset, not a magic button we cannot show. Partners should not reprint 'one free fix' as an unlimited legal or medical remediation. Compliance drafts stay labeled.

If the partner already builds sites in another tool, they can still attach a screenshot of a finding and a hand-built sample. They will feel extra product. They may still want Scout and Radar. We will not force Forge on a shop that fulfills elsewhere, and we will not pretend their Webflow file is our DEPLOY.

How do we end a partner fit that is wrong?

We say no and point at the compare page or the not-doing list. We do not keep a 'maybe later' that implies the dialer is coming. We do not collect their logo 'for the wall.' The wall is empty.

If they still want a seat as an ordinary tenant, they can join the waitlist. Partnership language stops. Acceptable use does not. A bad-fit partner who becomes a tenant and gates reviews is still a tenant we can lose.

If we were wrong about the fit, they can write again with a metro and a pillar. The second note should be shorter than the first. We remember the dialer ask.

How should a partner train a new hire on Nerxus?

Start with the four locks, Supervised, DEMO versus DEPLOY, and tenant isolation. Then run one hunt in their metro. Then attach one sample. Then make them revoke a /r token so they know artifacts die. Skip the values poster.

Give them /acceptable-use and /ai-info, not a swipe file of AI SDR mail. If they came from Instantly, show stop-on-reply and the domain gate before you show Nova. If they came from a gating shop, show the collect page first.