Field Notes

What we found, what we fixed first, and what it taught us.

One operator case study from the seat, field notes from current DySys work, and writing on revenue systems. Sector descriptors only, no client names, and nothing carries a date it cannot keep.

Operator case study

Before DySys, from the operating seat.

Starting condition, diagnostic, decision, measured result, from Duke's time running the revenue team. It is the one record backed by dated dashboards, board decks, and CRM exports, so it is the one that can carry the format honestly.

Industrial SaaS Operator case study

Reading a revenue system where the forecast and the outcome kept disagreeing

A PE-backed industrial software company with a credible plan, a full pipeline, and a quarter that kept coming in under call. The work was not adding activity. It was establishing which constraint was actually load-bearing, and getting leadership to commit to one first move.

Starting condition
Forecast confidence low, pipeline coverage nominally adequate, and no agreement across the leadership team on where growth was constrained.
Diagnostic
Built by hand in Salesforce: dashboards and reports to test stage integrity and deal-level evidence, with little admin or sales ops support. The lesson that stuck: you can only analyze as deep as what you capture.
Decision
One decision: what was holding the number, what to fix first, and which problems were downstream noise.
Measured result
Tracked against exit criteria set at the start, with the before-and-after evidence held in dated artifacts from the engagement.

Figures and dated evidence are held back. Duke will walk through the full story on a call.

Ask for the full read
Field notes

The pattern, published without the client.

Retrospective reads on engagements that work better as method writing than as case studies. No client names, ever.

Sports technology

GTM analysis for a sports tech startup

Segment prioritization and motion design for a B2C e-ski product creating a new market. AI was used to plan and run the diagnostic, facilitate a stakeholder alignment workshop, and build the early-stage GTM plan.

GTM StrategyICPStartup
Field note
Modular housing

Business and GTM consulting for a tiny home builder

Business model, design, pricing, and partner work alongside a go-to-market plan for a business founder. AI was used for diagnostics, risk assessment, product design, marketing content, planning, and program management.

Business ModelGTMStartup
Field note
Non-profit education

Knowledge management and operational efficiency for a non-profit girls school

Digital asset discovery, consolidation and ongoing management process to move a constrained budget toward students rather than administration. AI was used to scope the engagement, brief stakeholders, audit files and user access across Google Drive and Dropbox, and rank the structure, process and governance fixes.

OperationsProcessNon-profit
Field note
Oil & gas

Performance reporting for a small oil & gas company

Developed an agentic reporting layer that gave leadership one version of performance, replacing reconciled spreadsheets. AI was used to consolidate sources, analyze quarterly and annual performance, and produce summary and detail reporting for shareholders.

ReportingDashboardsEnergy
Field note
Field notes

Writing on revenue systems.

Short pieces on what we see across engagements: diagnostics, GTM structure, and where agentic AI genuinely helps.

Want the case study for your situation?

We will walk through the closest engagement to yours on an introductory call, including what did not work.