How we co-create with you.
We approach every engagement the same way: understand the real problem before recommending solutions, design something that fits your actual context, and deploy it iteratively — with value at every cycle. The examples below show what The North Star Method looks like in practice.
What is the Northstar Method?
The Northstar Method is a three-phase engagement structure — Discover, Design, Deploy — with clear deliverables and decision gates at each transition. The methodology prioritizes phased commitment over monolithic engagements, allowing clients to evaluate value before scaling investment.
The North Star Method
Three phases. Discover · Design · Deploy. Built for value at every cycle.
Whether the work is a four-week assessment or a multi-year program, the structure is the same: understand what's happening, design something that fits your context, and deliver it in stages. At every cycle, you have something you can use.
Many clients have lived through consulting engagements that disappear into a six-month black box and emerge with a 200-page report nobody reads. We don't work that way. Our engagements are structured in two-to-four-week cycles, and at the end of every cycle, you have something you can actually use — a finding, a quick-win recommendation, a working prototype, a documented process, a decision-ready briefing. Value compounds along the way; nobody waits for the final reveal.
This is sometimes called "agile" or "iterative" delivery. The technical name doesn't matter. What matters is: at every point of engagement, you're getting something useful.
Phase 1 — Discover
Typically 2–6 weeks
- Stakeholder interviews (board, leadership, frontline staff)
- Technology, process, and risk audit
- Funding and procurement landscape review
- Cycle deliverables: Findings memos at each two-week checkpoint
- Final deliverable: Comprehensive Assessment Report with prioritized findings
Phase 2 — Design
Typically 4–12 weeks
- Prioritized remediation or build plan
- Quick-win identification — what we implement during this phase, not after it
- Vendor and tooling recommendations (vendor-neutral)
- Funding pathway analysis (grants, contract vehicles, capacity-building funds)
- Final deliverable: 12-month implementation roadmap with funding strategy
Phase 3 — Deploy
Typically 6–24 months, retainer
- Hands-on implementation support
- Vendor selection and oversight
- Staff training and change management
- Fractional leadership functions where useful
- Ongoing measurement against the roadmap
- Cycle deliverables: Quarterly business reviews, monthly status reports
Most engagements share a sequence. First, stabilize—address what is broken and put the foundation on solid ground. Then modernize—replace aging or ill-fitting infrastructure with what the next stage requires. Finally, optimize—apply AI, automation, and other tools where they can improve results. Skipping the first two steps is a common reason AI implementations fail.
Each phase justifies the next. Clients who only need Phase 1 get a real deliverable they can act on without us. Clients who go further do so because the work earned it. Nobody is locked in.
The North Star Method in practice
The following scenarios show how The North Star Method applies to four common engagement types. Situations are composites drawn from real-world contexts; the engagement structures show how we'd structure the work.
Operational and Financial Controls Reset for a Public Agency
A mid-size public agency had experienced repeated technology incidents over three years. The previous CEO had circumvented digital financial systems by requiring handwritten receipts—creating untraceable access points and an audit trail that did not exist. A new CEO was inheriting an organization with unresolved infrastructure concerns, financial controls failure, and unknown depth of damage.
The work called for more than an IT repair. It joined three issues: a history of technology incidents, an internal financial controls failure, and a leadership transition where the new CEO needed clarity before making major decisions. The engagement scope was a trust, governance, and infrastructure reset.
Infrastructure, access-control, and incident-history review. Financial controls audit. Stakeholder interviews. Deliverable: a comprehensive risk and gap report with prioritized findings.
Prioritized remediation plan across infrastructure, financial controls, and operations. Review of relevant federal grants and capacity-building funds. Board-ready presentation.
Oversight of vendor selection, financial-system replacement, access controls, recovery planning, and staff training. Ongoing operating guidance for leadership.
If the agency has a pending federal modernization grant, we help scope the application and write the statement of work. Federal funding and audit requirements can make this work essential rather than discretionary.
AI Implementation for a State Health & Human Services Agency
A state HHS agency facing pressure from the legislature to adopt AI-enabled fraud detection in its Medicaid program — alongside vendor proliferation, governance uncertainty under emerging state AI legislation, and a procurement environment where the wrong contract vehicle could lock the agency into a multi-year decision before the technology was understood.
The pressure point looked like "buy AI fraud detection." The actual problem was: how do you adopt AI in a high-stakes, federally-overseen, citizen-affecting program without locking yourself into the wrong vendor, the wrong architecture, or the wrong governance posture before you've had time to learn? The engagement we proposed wasn't an AI build — it was AI strategy and procurement architecture, with the build coming later.
Stakeholder interviews across agency leadership, program oversight, IT, legal, and the legislative sponsor's office. Federal precedent analysis (CMS AI fraud detection, Florida 40x ROI). State governance landscape review. Coalition map.
Pilot Implementation Plan defining MVP scope, success metrics, governance frameworks, and human-in-the-loop architecture. Vendor evaluation framework. Contract vehicle recommendation. Funding pathway analysis.
Independent vendor-neutral oversight of the build. Workforce AI literacy program for agency staff. Public-facing AI notice and acceptable-use policy implementation. Quarterly readouts to legislative sponsors and oversight committees.
A federal precedent—CMS-disclosed AI fraud detection saving about $2B in twelve months—helps the agency assess the trade-offs of action and inaction. A bipartisan legislative committee already organized around the issue makes the work legible and politically supported. State AI legislation gives the agency a defensible governance framework.
Operational Modernization for a Growing Mid-Market Business
A growing business at the inflection between founder-run and professionally-run, struggling with high turnover, manual processes, and the realization that the systems that got them here would not get them to the next stage. Management was considering enterprise-grade software and bracing for a six-figure procurement decision.
Most firms would have led with software recommendation. We saw a process problem masquerading as a technology problem. Implementing enterprise software on top of unclear processes amplifies the chaos rather than fixing it. The engagement we proposed started at process documentation and only got to technology in Phase 2.
Stakeholder interviews. Process mapping for the three highest-friction workflows. Technology stack review. Deliverable: process audit report.
Implement two quick-win process changes that address 60% of the friction with no software spend. Design the technology layer to fit the redesigned process. Vendor evaluation and recommendation.
Technology rollout. Staff training and change management. Quarterly business reviews. Transition to advisory by month 12.
The original procurement budget would get smaller, not bigger — because the right technology, scoped to a redesigned process, costs less than the wrong technology scoped to chaos. The change management work would make the actual technology rollout uneventful — the opposite of what clients typically expect.
Fractional CFO + COO Coverage for a Nonprofit in Leadership Transition
A mission-driven nonprofit had two simultaneous executive openings — CFO and COO — at a moment when the organization was managing federal grants with zero margin for compliance error and a board newly attentive to financial controls after a previous administration's lapses. A traditional executive search would take 6–9 months per role. The organization could not wait.
Most consulting firms would have positioned a "transition support engagement." We saw that as half the answer. The board didn't need an engagement; the organization needed executives. We proposed fractional CFO and COO coverage — fractional in time commitment, full in scope, embedded enough to be accountable for outcomes, lightweight enough to be sustainable while permanent search happened in parallel.
Financial controls audit. Operational risk assessment. Immediate-term grant compliance review. Identified one open compliance exposure that, left another quarter, could have triggered a federal audit. Resolved.
Embedded as fractional CFO (~16 hours/week) and fractional COO (~12 hours/week). Built monthly board-reporting cadence. Implemented grant tracking and reporting infrastructure. Designed and ran the search for permanent hires in parallel.
Stepped down to advisory cadence as permanent leadership took the seat. Closed engagement with a clean handoff document and standing on-call availability for the first 90 days of the new CFO's tenure.
A board weighing emergency interim CFO coverage may find fractional leadership a practical way to maintain oversight. Federal grant compliance work can sometimes be funded through allowable indirect costs. The hand-off document becomes the onboarding curriculum for both permanent hires.
Discovery questions we bring to every first conversation
We don't lead with solutions. We lead with questions.
For every first conversation
- —What does success look like to you in 6, 12, 24 months?
- —What's been tried before? What worked, what didn't, why not?
- —Who are the stakeholders that need to be on side for this to work?
- —Where's the urgency coming from — is it real, or manufactured?
- —What's the budget reality — what funding sources are available, what's off-limits?
For public-sector clients, we add
- —What governance and procurement constraints shape what's even possible?
- —Who's the legislative or executive sponsor? What's their political coalition?
- —Are there federal program oversight or compliance requirements that make this non-optional?
- —What's the procurement vehicle, and is the scope sized to fit it?
For nonprofits, we add
- —What grants, capacity-building funds, or insurance products could support this work?
- —What does the board know, and what do they need to know?
- —Are there audits, funder reviews, or regulatory deadlines on the horizon?
For businesses, we add
- —What's the actual bottleneck — is it process, technology, people, or capital?
- —What's your growth curve assumption, and is the system you're building for the curve you're on or the curve you wish you were on?
- —What does "scale" actually mean in your context — revenue, geography, headcount, complexity?
How engagements start
We begin by understanding the work, then document the proposed scope and timeline before any work begins. Engagements account for your goals, schedule, and funding context—whether that is a state or federal contract vehicle, a federal grant, capacity-building funds, or a direct engagement budget.