OPERATING PLAN

Learn the stack fast, prove revenue motions locally, then scale the ones that work.

Fremont should be the laboratory for the North American playbook. The first 90 days should establish technical credibility, partner and account baselines, and live commercial evidence. Year one should scale only the channels and ICPs that produce healthy revenue.

90-DAY SPRINT

Three phases with founder-visible outputs.

The goal is not a 90-day strategy project. It is to learn while selling and leave each phase with measurable pipeline, partner and product feedback.

DAYS 1-30 · LEARN + BASELINE

Become technically credible and map reality.

Provision Xthings One / Station and personally understand core commercial device flows
Shadow Product, Solutions, Marketing, Sales and Operations on live opportunities
Learn current pricing, margins, partner program, support boundaries and implementation constraints
Audit existing partners by sourced revenue, activation and opportunity history
Audit Closed Lost, stalled and nurture opportunities for reactivation
Map first 30 high-potential integrators / MSPs and priority direct accounts in the Bay Area
Define first version of Partner IQ / Account IQ using real historical evidence

DAYS 31-60 · ENGAGE + VALIDATE

Run the motions against live buyers.

Launch targeted partner and direct-account outreach around active triggers
Run joint account planning with the strongest existing partners
Stand up a clean deal-registration and next-action discipline in CRM
Launch first structured pilots with defined success criteria and decision dates
Create product feedback cases for repeated API / integration blockers tied to revenue
Test inbound routing for partner applications, developer interest and enterprise demos

DAYS 61-90 · CLOSE + CHOOSE

Prove what deserves scale.

Close the first partner-led and direct opportunities supported by real pipeline timing
Compare partner types and ICPs by conversion, cycle time, margin and support burden
Identify the best 2-3 repeatable GTM motions for North America
Turn first wins into reference, co-sell and expansion plans
Present founder review: what converts, what stalls, product gaps, channel conflicts and next 12-month priorities

$2M QUOTA PLAN

Base case: 12 meaningful wins across three motions.

The attached interview research models a $2M annual target. I would use the math as a planning case, then replace the assumed contract values and close rates with Xthings' actual compensation and sales data.

INTEGRATOR / ECOSYSTEM4 × $180K = $720K

Four partner-led commitments or sourced enterprise programs with meaningful hardware + cloud value.

PROPERTY / MULTIFAMILY4 × $173.2K = $692.8K

Four medium-size property deployments modeled on the 300-unit worked example in the research.

ENTERPRISE / FACTORY4 × $183K = $732K

Four high-security enterprise deployments modeled on the research's manufacturing case.

BASE-CASE TOTAL$2.145M

107% of a $2M target, before upside from expansions, software growth or additional partner-sourced projects.

Q1$300K

Pipeline cleanup, partner activation, lighthouse pilots.

Q2$500K

First repeatable partner and property motions.

Q3$550K

Construction / retrofit conversion and multi-site expansion.

Q4$650K

Enterprise budget cycles and larger year-end programs.

IF QUALIFIED WIN RATE = 20%~$10.7M pipeline

25%~$8.6M pipeline

30%~$7.1M pipeline

35%~$6.1M pipeline

Quota discipline: I would manage to qualified pipeline coverage, not a raw opportunity count. The exact coverage multiple should be set from Xthings' historical win rate by source, ICP and deal stage.

DAY-30 EXECUTIVE OUTPUTS

Each leader should get something decision-ready.

The first month should not end with a strategy presentation. It should end with operating information leadership can use immediately.

CEOWhere should we place the next commercial bets?

Partner productivity baseline, best ICP evidence, pipeline coverage, deal economics and the 2-3 motions worth funding harder.

STRATEGIC PARTNERSHIPSWhich partners deserve attention?

Current partner segmentation, activation gaps, target shortlist, co-sell opportunities and channel-conflict issues.

PRODUCT MARKETINGWhat proof is missing from the field?

Top objections, integration questions, competitive gaps, pilot requirements and the sales assets most likely to improve conversion.

BASELINE FIRST

Do not reverse-engineer quota from the compensation line.

The posted OTE is aggressive, but quota and revenue credit cannot be inferred responsibly without the comp plan. By Day 30 I would establish the commercial facts and set targets with leadership.

REVENUE CREDITWhat counts?

Hardware revenue, gross margin, software ARR, partner-sourced revenue, multi-year TCV and renewals may be credited differently.

DEAL ECONOMICSWhat is a good deal?

ACV / TCV, hardware margin, software attach, discounting, integration effort and support burden.

PARTNER BASELINEWho is actually productive?

Signed, trained, active, sourcing, co-selling, closing and expanding are different states.

SALES BASELINEWhere does conversion break?

Source to meeting, qualification, pilot, proposal, security / legal review and close.

ICP BASELINEWhere do we win?

Vertical, deployment type, incumbent technology, protocol environment and buyer role.

CAPACITYHow fast can we responsibly scale?

Solutions engineering, onboarding, inventory, field support and product roadmap constraints.

DAY-30 OUTPUTA founder-approved revenue model and operating target.

Set quota coverage, partner productivity targets, direct-sales activity and pilot expectations from Xthings' real economics, not outside assumptions.

YEAR-ONE SCOREBOARD

Scale what creates durable business.

These are the metrics I would expect to review with leadership monthly, regardless of the final quota number.

PARTNER-SOURCED PIPELINERevenue created by the ecosystem

Qualified pipeline and closed revenue sourced / influenced by partner type.

ACTIVE PARTNER RATESigned to productive

Percent of partners generating real opportunities within an agreed activation window.

TIME TO FIRST DEALOnboarding efficiency

How long it takes a new partner to move from agreement to first paid deployment.

PILOT TO PAIDTechnical proof quality

Whether evaluations are connected to a real buying decision.

WIN RATE + CYCLECommercial velocity

By direct vs partner, ICP, product mix and reason won / lost.

SOFTWARE ATTACHRecurring value

Share of eligible hardware deployments carrying ongoing Xthings Cloud revenue.

GROSS MARGIN / SUPPORTHealthy revenue

Discount, partner incentive, integration work and post-sale support cost.

EXPANSIONSecond site / second account

The clearest signal that a partnership or deployment has become repeatable.