A PERSONAL POV FOR MERIT HOLDINGS

Build the GTM engine.
Create the next
vertical advantage.

Your GTM Engineer posting brought Merit to my attention. Whether that role is still open or already filled, I’d welcome a conversation about contributing through Agilidy: fractional GTM ownership, portfolio support and vertical-specific agentic IP with a Microsoft co-selling strategy.

See the work My answers to your three questions ↓

Jason Wickman · Founder, Agilidy · Former Microsoft Dynamics Sales Director

25+ years across CRM, sales & technologyCommercial judgment + hands-on buildingFractional / contractor-to-hire / open to FTE

WHY YOUR GTM ENGINEER POSTING RESONATES

This is closely aligned
with what I already do.

Your posting connects sales, marketing and technology through durable, AI-first workflows. That is where I’ve spent my career, and where I’m building now.

I bring the business context to decide what is worth building, and the hands-on ability to put it into practice. I work with a handful of clients through Agilidy and am developing my own agentic products and intellectual property.

The role may already be filled. If it is, I’d welcome the opportunity to complement the team around a focused sourcing or portfolio GTM outcome. If it remains open, I’m interested in discussing fractional, contractor-to-hire or full-time arrangements. Either way, I see potential to explore vertical agentic IP and Microsoft co-selling together.

The posting that started this POV

A SHARED INTEREST. SEVERAL WAYS TO CONTRIBUTE.

Support the team.
Build assets that compound.

Strengthen the sourcing workflow.

Understand what the team already has in place, then agree where I could own a focused improvement alongside the current owner.

Agree target criteria, lifecycle stages and an evidence standard

Connect research, enrichment, prioritization and relationship history

Prepare relevant outreach with human approval and clear ownership

Instrument quality, cost, failures and progression to diligence

Proposed measures

Qualified founder conversations · Research time · Data accuracy · Diligence progression

YOUR POSTING’S THREE QUESTIONS. MY BUILDER’S MINDSET.

A little more than
my résumé can tell you.

What’s the last new skill you learned for fun and how did you tackle it?

From playing songs to writing them.

Songwriting. I’ve been playing for years, but writing my own songs was a new challenge. I tackled it by turning that long-standing interest into a concrete creative project: original songs that ultimately became a published album. There’s something energizing about moving from interpreting someone else’s work to putting your own ideas into the world.

Curiosity becomes something tangible.

What accomplishment didn’t make it on your resume but tells a story about you?

An entire album. Four songs in Nashville.

I published an entire album, and four of my songs are being reviewed in Nashville. That probably tells you something a résumé doesn’t: when an idea matters to me, I want to see it through to something other people can experience. Publishing the album is the accomplishment I’m proud of.

Follow-through matters as much as the idea.

What AI/GTM workflow are you most proud of? Describe it without breaking any NDAs.

Turning account intelligence into action.

The work I’m most proud of is Orkastra.AI and OrkastraD365, particularly the Microsoft co-selling motion. The workflow connects account research and supporting evidence to a relevant sales play, a buyer-facing value story and a reviewed next action. My broader portfolio includes OrkastraGRO, OrkastraRX and Vibe365. Together, they reflect what interests me most: building reusable intelligence, adapting it to a vertical and making it useful in the way revenue teams actually work.

Research → judgment → owned action → learning.

THE WORK BEHIND THE POINT OF VIEW

Five expressions of
one operating idea.

Bring context, intelligence and execution together. Adapt the workflow to the industry and the people using it.

LEAD EXAMPLE · MICROSOFT GTM

OrkastraD365

Account evidence becomes a Microsoft-relevant sales play, a reviewed pursuit and a clear next action.

For Merit: reuse the research, prioritization and execution patterns; develop vertical offers with a credible Microsoft sales story.

Explore OrkastraD365

OrkastraD365 public product screenshot — Existing public product capture · click to enlarge. Displayed scores and projections are illustrative, not validated results.

Implemented workflows reviewed in source. Tenant configuration, live integration behavior and offer eligibility require validation.

THE ADDITIONAL OPPORTUNITY / PROPOSED

Vertical agentic IP.
A Microsoft route
to market.

I can help Merit’s companies turn domain expertise into a repeatable agentic offering, and make that offering easier for Microsoft sellers and partners to understand, demonstrate and pursue.

My Microsoft background and OrkastraD365 work connect the product conversation to the commercial motion: who buys, why it matters, which seller should care and what happens next.

Choose the vertical problem

Select a frequent, valuable workflow with accessible data and a clear buyer.

Build the agentic IP

Combine domain context, tools, evaluation and human approval around a measurable task.

Package the offer

Validate architecture, deployment, pricing, support and the relevant Marketplace path.

Enable the co-sell motion

Develop seller-ready proof, buyer value, account overlap and a specific joint pursuit.

Microsoft co-sell readiness is an outcome to work toward. Offer type, technical validation, commercial requirements and seller participation must be confirmed for each solution. A Teams or Copilot integration alone does not establish co-sell eligibility.

AN ILLUSTRATIVE ENGAGEMENT / SCOPE TO AGREE

Start with a focused mandate.
Earn the broader scope.

Agree the outcome. Build the first loop.

Understand the current team, stack and priorities. Agree one sourcing or portfolio GTM outcome and establish a baseline. Review existing Agilidy IP and agree what may be used, licensed or newly developed.

What we take forward

Working workflow v1, evidence checklist, baseline scorecard and a clear IP/work scope.

Proposed sequence. Capacity, milestones and measures agreed together.

HOW WE COULD WORK TOGETHER

Open on structure.
Clear on the conversation.

Fractional

Own an agreed outcome and delivery cadence through Agilidy, working alongside Merit’s existing team.

Contractor-to-hire

If a permanent role is available and of mutual interest, start with real work and revisit the structure at an agreed milestone.

Full-time

If there is a suitable opening, I’m open to FTE. First, I would want to discuss Agilidy, the products and IP I’m building, and how those commitments fit with Merit.

Put the IP conversation on the table early.

Agree the treatment of existing products and IP, any licensed components, newly commissioned work, ongoing business commitments and potential conflicts before choosing the engagement structure. No transfer of existing IP is assumed by this proposal.

LET’S EXPLORE THE FIT

Your current priorities.
My operating experience.
Something useful to build together.

Whether the GTM Engineer role is open, filled or has evolved, I’d welcome a conversation about how we could work together. Let’s start with your current priorities and where my experience and developing IP could be useful.

Discuss the opportunity with Jason

Build the GTM engine.Create the nextvertical advantage.

This is closely alignedwith what I already do.

Support the team.Build assets that compound.