Nexuscore
ICP, Signal & Outreach Discovery
This form covers the business side of Nexuscore only: VPS, bare metal, and web hosting for companies, developers, and agencies. Game server hosting is out of scope here. The questions build three things: the ideal customer profile, the signal map that tells us a buyer is ready, and the rules we'll use to search for, qualify, contact, and book those buyers. Every answer becomes a filter, a search phrase, a signal to monitor, a scoring rule, or a line in a message, so specifics beat generalities every time. Give us numbers, named examples, links, and the literal words your customers use wherever you can.
This is a long form on purpose: 119 questions, roughly two to three hours in total, built to be done over several sittings. All questions are required. Answers save automatically on this device, so stop and return anytime, then download or print once every answer is in.
How the form is organized
A working reference for the search, the scoring, and the outreach, drawn from the Nexuscore research and refined by your answers above. Rows that point at a question are our current read, not a settled fact.
| Signal | Indicator we target |
|---|---|
| Primary segment | Developers and small software companies running web apps, APIs, and SaaS backends that outgrew shared hosting or overpay a hyperscaler; confirmed in Q13 and Q21 |
| Agency and MSP segment | Web agencies, WordPress shops, and MSPs hosting client sites and workloads, often on reseller or white label terms; open until Q17 is answered |
| Small business segment | Local and online businesses that need WordPress, WooCommerce, or a simple US hosted site and a human who answers |
| Organization size and stage | Solo to about 50 people, bootstrapped or lightly funded; no enterprise procurement, RFPs, or compliance audits; confirmed in Q23 and Q24 |
| Account numbers | Traffic, sites or servers, and current infrastructure spend above the floor set in Q25 |
| Budget band | $5 to $40/month VPS is self serve; bare metal, agency, and reseller accounts are where outbound pays; the floor for a human conversation is set by Q30 |
| Technical posture | Root access and self service by default; a managed persona only if Q09, Q40, and Q41 say so |
| Geography | US and North America first, with Chicago latency and a US data location as the story; exclusions from Q26, who cares from Q27 |
| Current provider | Hyperscaler overspenders, developer clouds, managed WordPress, shared hosting, and servers in closets; the providers you win from are confirmed in Q29 |
| Trigger events | Cloud bill shock, a price increase or acquisition at the old host, an outage during a launch or sale, a DDoS or security incident, outgrowing a plan, a developer leaving, a new launch, a renewal date; listed in Q45, timed by Q46 |
| Top signals and how we verify them | Your three most predictive signals (Q52) each paired with the public evidence that confirms it (Q53) |
| Freshness window | How old a signal can be before we drop it, set in Q57 |
| False positives | Things that look like intent but aren't, filtered out before contact; listed in Q58 |
| Where to look | Developer and hosting communities, agency and MSP directories, startup and launch lists, competitor review pages, hiring posts, Louisville and Chicago business and tech groups, and your own lapsed pipeline (Q60 to Q67) |
| Technographic tells | The network a site or app resolves to, shared hosting and control panel fingerprints, slow page response, recent migrations; detailed in Q63 |
| Scoring and thresholds | Points by segment, size, provider, workload, trigger, geography, and title (Q80); one bar to contact, a higher bar to ask for a meeting (Q81) |
| Human first accounts | Large accounts, multi site agencies, referrals, and anyone you know get a person, not a sequence; the line is drawn in Q82 |
| Disqualifiers and suppression | Enterprise procurement, compliance you can't paper, abuse prone workloads, regions you don't serve, managed everything at a self serve price (Q78); plus every relationship on the suppression list (Q83) |
| Offer and proof by segment | Each segment gets its own proof point (Q86) and its own call to action (Q87) |
| Booking definition and gate | What counts as a booked meeting (Q94) and what must be confirmed before one is booked (Q95) |
| Capacity fit | Volume tuned to a 1 to 10 person team; monthly targets set from your answers to Q111 and Q104 |