Internal Tools

Summary

Asymmetric's internal tooling centers on X-Ray, an AI-powered client management platform that consolidates data from approximately 15 external platforms and surfaces prioritized opportunities, call intelligence, and financial metrics in a single interface. X-Ray launched to the full team in mid-December 2025 and is the primary vehicle for reducing context-switching across client accounts. The platform's biggest operational risk is not its feature set — it's permissions: admin-level testing masks access failures that surface only when non-admin users attempt to load client data, as demonstrated by a 403 error blocking Bluepoint access for a secondary account manager. A second standalone tool, the OKR & Client Health App, handles health tracking and goal management separately, and the relationship between X-Ray and the Meridian Marketing Dashboard remains architecturally ambiguous.

Current Understanding

X-Ray is the load-bearing internal tool: everything else in the stack either feeds into it or handles a function it doesn't cover.

X-Ray: Platform Scope and Architecture

X-Ray pulls data from approximately 15 external platforms into a single interface, with confirmed integrations including Google Ads, HubSpot, CallRail, WordPress, and Google Search Console ^[1]. The platform was built by Mark Hope and launched to the Asymmetric team during the week of mid-December 2025, timed to coincide with the Q4 OKR review period ^[2].

The core value proposition is eliminating the tab-switching and manual data assembly that characterizes multi-platform client management. Rather than logging into Google Ads, then HubSpot, then CallRail separately, account managers get a unified view with AI-generated analysis layered on top. This is the right architectural instinct — the friction cost of context-switching across 15 platforms is real and compounds across a full client roster.

AI Analysis Layer: Opportunities, Call Intelligence, and Financial Modeling

X-Ray's AI layer operates across three distinct domains. First, opportunity detection: the platform generates prioritized opportunities scored 1–100 across categories including Blue Ocean, Competitive Blind Spots, Content Voids, and Peak Performance, with highest-value items surfaced at the top ^[3]. Second, call intelligence: X-Ray analyzes CallRail transcripts to classify each call by intent, sentiment, urgency, and sales readiness ^[4]. Third, financial modeling: the platform calculates Customer Lifetime Value against Customer Acquisition Cost with sensitivity analysis built in ^[3].

The opportunity scoring system is the most operationally significant of these. A 1–100 score with named categories gives account managers a defensible prioritization framework rather than a raw list of data points. The risk is score calibration — if the model weights categories incorrectly for a given client's business model, the ranked list misleads rather than guides.

Workflow Integration: ClickUp Automation

X-Ray closes the loop between insight and execution by automatically creating ClickUp tasks with pre-generated subtasks directly from identified opportunities ^[5]. This is the most consistently documented feature across sources — three separate fragments reference it, suggesting it's a core workflow rather than an edge capability. The practical effect is that an account manager can move from "X-Ray flagged a content void opportunity scored 87" to "ClickUp task created with subtasks" without leaving the platform.

OKR & Client Health App: Separate Architecture, Deliberate Design

The OKR & Client Health App is a standalone React application with its own API and domain — not a ClickUp plugin and not a module within X-Ray ^[6]. It entered pilot phase with Isalia as the designated pilot user as of November 14, 2025. The app uses manual update workflows by design: the act of actively touching OKRs is considered valuable in itself, not a friction point to be automated away ^[6]. This is a meaningful architectural choice — it means the OKR app will never auto-sync from X-Ray data, which is either a feature or a gap depending on how the team uses it.

The X-Ray / Meridian Naming Problem

A genuine architectural ambiguity exists in the source material. X-Ray is described as an "AI-powered client management platform" for centralizing client performance data ^[3], while the Meridian Marketing Dashboard is described as "an internal application designed to consolidate all client marketing data" with overlapping features including opportunities, ClickUp integration, and Ask AI ^[7]. The demo dates — X-Ray on 2026-01-16, Meridian on 2026-01-13 — suggest these may be the same platform at different stages, or closely related versions of the same codebase. This is unresolved and matters for onboarding: a new team member reading both documents would not know which tool to open.

What Works

Opportunity scoring with named categories. Classifying opportunities into Blue Ocean, Competitive Blind Spots, Content Voids, and Peak Performance gives account managers a shared vocabulary for prioritization conversations. A numeric score alone is ambiguous; a score plus a category tells you both how important and what type ^[3].

ClickUp task creation from opportunities. The direct path from identified opportunity to ClickUp task with pre-generated subtasks eliminates the manual translation step that typically causes insights to die in dashboards. Documented across three sources, this is the most validated workflow in the platform ^[5].

Call transcript classification. Analyzing CallRail transcripts for intent, sentiment, urgency, and sales readiness converts unstructured call data into structured signals that can inform account strategy. This is particularly useful for clients with high inbound call volume where manual review is impractical ^[4].

CLTV vs. CAC with sensitivity analysis. Building financial modeling directly into the platform means account managers can run "what if" scenarios without exporting to a spreadsheet. The sensitivity analysis component is the differentiator — it surfaces the range of outcomes, not just the point estimate ^[3].

Manual OKR update workflows. The deliberate choice to require manual updates to the OKR app creates a forcing function for account managers to actively engage with client goals rather than passively observe auto-synced numbers. Based on a single engagement with the OKR app design rationale, but the logic is sound ^[6].

Consolidating ~15 platforms into one interface. The reduction in context-switching is the foundational value of X-Ray. Every minute not spent logging into separate platforms is a minute available for analysis ^[2].

What Doesn't Work

Admin-only permission testing. Testing X-Ray access from an admin account masks permission failures that non-admin users will encounter. Karly received a 403 Forbidden error when attempting to access Bluepoint data despite being assigned as secondary account manager in the admin panel — a failure that would not have been visible during admin-level QA ^[8]. Any new account assignment must be verified from the assigned user's account, not the admin's.

Admin panel assignment as a proxy for API permissions. Assigning a user to an account in the admin panel does not guarantee that underlying API permissions are correctly propagated ^[8]. These are two separate permission layers, and the admin UI does not surface failures in the API authorization layer. This is a systemic gap, not a one-time bug.

Spare-hours development cadence. X-Ray development has been done in spare hours rather than focused blocks, which has caused regressions ^[4]. Features that worked in one session break in the next. This is a resource allocation problem, not a technical one — the platform needs dedicated development time to stabilize.

Data connections at launch. At the time of the January 2026 demo, the attribution model and paid media view had disconnected data connections ^[4]. Launching with known broken integrations creates trust problems with the team — if two visible features are broken, users will question the reliability of features they can't directly verify.

Unclear tool naming and architecture. The overlap between X-Ray and the Meridian Marketing Dashboard — same features, similar descriptions, three-day gap in demo dates — creates genuine confusion about which tool to use and what each one does ^[9]. This is a documentation and naming problem that compounds onboarding friction.

Patterns Across Clients

Permission failures surface at the client level, not the admin level. The Bluepoint 403 error is the clearest example: Karly was correctly assigned in the admin panel, but the API layer had not propagated the permission, and this was only discovered when she attempted to access the account ^[8]. The pattern suggests that any permission change should be validated by the affected user, not assumed complete after admin configuration.

Role-based access control is a recurring concern across clients. Both Bluepoint (403 error on X-Ray access) and Ahs (role-based access for cost visibility) surface access control as an operational friction point ^[10]. This is not a coincidence — it reflects a platform architecture where permission layers are not fully synchronized, and where the consequences of misconfiguration are invisible until a non-admin user hits a wall.

Internal tools are launched before they are stable. X-Ray launched in mid-December 2025 with known regressions caused by spare-hours development, and the January 2026 demo showed disconnected data connections in two features ^[11]. The pattern is: launch to create accountability and team adoption pressure, then stabilize. This works if the team understands the tool is in active development; it backfires if they treat demo-state features as production-reliable.

All internal tools route execution through ClickUp. X-Ray creates tasks from opportunities, the Meridian dashboard integrates with ClickUp, and the OKR app connects to ClickUp for workflow management ^[12]. ClickUp is the execution layer; the internal tools are the intelligence layer. This is a coherent architecture, but it means ClickUp reliability is a dependency for the entire internal tooling stack.

AI analysis is embedded at every layer. Opportunity scoring, call transcript classification, Ask AI, and health score generation all appear across the tool suite ^[13]. The consistent pattern is AI as an analysis layer on top of raw platform data, not AI as a replacement for human judgment. The outputs are scores and classifications, not autonomous decisions.

Exceptions and Edge Cases

The OKR app's deliberate resistance to automation. The general pattern across internal tools is automation wherever possible — ClickUp task creation, AI scoring, data sync. The OKR app breaks this pattern intentionally: manual updates are a feature, not a bug ^[6]. This exception is architecturally significant because it means the OKR app will not converge with X-Ray's automation-first approach, even as the two tools address adjacent problems.

X-Ray was intended to replace a planned ClickUp-based client health dashboard, but the OKR app now occupies that space. The original plan was for X-Ray to handle health tracking; the OKR app emerged as a separate standalone application serving similar functions ^[14]. The result is two tools with overlapping scope and no documented integration between them.

Attribution and paid media views were non-functional at demo time. While X-Ray's core features (call analysis, opportunity scoring, ClickUp integration) were demonstrated as working, the attribution model and paid media view had disconnected data connections as of January 2026 ^[4]. For clients where paid media is the primary channel, this means X-Ray's most relevant view was unavailable.

Admin panel assignment and API permissions are independent systems. The general assumption — that assigning a user in the admin panel grants them access — is false in X-Ray's current architecture. The 403 error on Bluepoint demonstrates that these are separate permission layers that can fall out of sync ^[8]. This exception to expected behavior is the highest-priority operational risk in the current tool state.

Evolution and Change

The internal tooling stack is young and moving fast. The OKR & Client Health App entered pilot phase in November 2025 with a single pilot user (Isalia). X-Ray launched to the full Asymmetric team in mid-December 2025 — roughly one month later. The January 2026 demo showed a platform with most core features functional but two data connections broken, consistent with a tool in active stabilization rather than mature production state.

The naming ambiguity between X-Ray and the Meridian Marketing Dashboard — with demos three days apart in January 2026 — suggests the platform may have been rebranded or restructured during this period. If X-Ray and Meridian are the same tool at different naming stages, the earlier "Meridian" documentation is effectively superseded. If they are distinct tools, the overlap in described features needs architectural resolution.

The most significant near-term change signal is the explicit acknowledgment that spare-hours development has caused regressions and that dedicated development blocks are needed to stabilize the platform ^[4]. Whether that resource allocation shift happens will determine whether X-Ray matures into a reliable production tool or remains in a perpetual beta state. No evidence yet on which direction this has resolved.

Gaps in Our Understanding

The X-Ray / Meridian relationship is unresolved. We do not know whether these are the same platform, a rebrand, or two distinct tools with overlapping scope. Every recommendation about which tool to use for what purpose depends on this answer.

No evidence on X-Ray's reliability post-January 2026. All source material dates to January 2026 or earlier. We don't know whether the broken attribution and paid media connections were fixed, whether the permission architecture was corrected, or whether dedicated development time was allocated.

No client-facing usage data. All observations are internal — how the tools were built and what they're designed to do. We have no evidence on how account managers are actually using X-Ray day-to-day, which features get used versus ignored, or whether the opportunity scoring is influencing real prioritization decisions.

OKR app adoption beyond the pilot. The pilot launched with Isalia in November 2025. We have no evidence on whether adoption expanded beyond the pilot user, what the pilot revealed about the tool's usability, or whether the manual update workflow held up under real usage.

Permission architecture documentation. The 403 error revealed that admin panel assignment and API permissions are separate systems, but we have no documentation of how to correctly configure both layers, what the correct sequence is, or whether there's a verification step built into the admin workflow.

Open Questions

Are X-Ray and the Meridian Marketing Dashboard the same platform? The three-day gap between demos and the feature overlap suggest convergence, but this needs explicit confirmation. If they're the same tool, the Meridian documentation should be archived or redirected.

Has the permission propagation bug been fixed, or is it a structural limitation of the current architecture? If it's structural, every new account assignment requires a verification step from the assigned user's account — this needs to be a documented SOP, not tribal knowledge.

What is the accuracy rate of X-Ray's opportunity scoring? A 1–100 score is only useful if it's calibrated. Do higher-scored opportunities actually convert to better client outcomes? Without validation data, the scoring system is a prioritization heuristic, not a validated model.

Does the call transcript classification (intent, sentiment, urgency, sales readiness) produce actionable output at the account level, or is it primarily useful in aggregate? Single-call classification may be too noisy to act on; the value may emerge only when looking at patterns across many calls for a single client.

When will the attribution model and paid media view have functional data connections? For clients where paid media is the primary channel, X-Ray's utility is significantly reduced without these views.

What is the integration path between X-Ray and the OKR app? If both tools are in active use, account managers are maintaining two separate systems with no documented data flow between them. Is this intentional or a gap to be closed?

Has dedicated development time been allocated to X-Ray stabilization? The spare-hours development model was identified as the cause of regressions. Whether this changed after the January 2026 demo determines the platform's reliability trajectory.

Related Topics

Sources

Synthesized from 7 Layer 2 articles, spanning 2025-11-14 to 2026-04-08.