Assessment · GTM operations readiness
Where would Nexus start for you?
Nine inputs. A readiness score you can see the working for, the blockers standing between your objectives and a running system, and a first-90-days configuration ordered the way Nexus would run it. Everything stays in this browser until you choose to save or send it.
STEP 01 · UNDERSTAND
Who is this for?
The starting configuration differs.
STEP 02 · UNDERSTAND
What do you want to change first?
Up to three. Each one maps to agents in the model.
STEP 03 · UNDERSTAND
What do you run on?
The fit check reads this: which recommended agents are already connected, which need one grant.
STEP 04 · DIAGNOSE
How does the work run today?
Honest answers score lower and plan better.
The rubric
How the score is computed (100 points)
Deterministic rules over your answers and the capability model — no model call. The same answers always give the same score, and a saved evaluation is re-scored server-side from the answers, so what you share is what Effiqs sees.
| Dimension | Max | How |
|---|---|---|
| Direction | 10 | 3 for stating who you are, 7 for at least one objective. |
| Foundation | 20 | A current written strategy: 20. Partial or stale: 10. None: 0. Every Nexus agent reads the strategy first, so this is the largest single lever. |
| Measurement | 20 | Trusted conversion tracking: 20. Partial: 10. None: 0. |
| Connectivity | 20 | The share of your recommended configuration that is already connected for your stated stack (admin-credentialed connectors count as connected — Nexus brings them). No stack stated: 0. |
| Rhythm | 15 | Weekly reporting: 15. Monthly: 12. Quarterly or ad hoc: 6. None: 0. |
| Operations | 15 | Content on a calendar: 8 (sometimes: 4). Work in shared systems: 7 (mixed: 3). |