Where rigor
meets execution.
Across every discipline.

Context

The client was a federal program office operating under FFMIA and FASAB standards, with a recent history of management letter findings and the threat of a qualified opinion if the same deficiencies surfaced again. Leadership wanted to move from reactive remediation to a sustainable audit-readiness posture — one that didn't depend on the same handful of staff working seventy-hour weeks every fall.

The Challenge

Three operational realities made this difficult. First, the program office's workforce had limited financial-audit experience — most were policy and operations professionals who had never sat across from an external auditor. Second, the prior-year findings touched control areas that crossed multiple workstreams and required cross-functional remediation, not just a fix in a single team. Third, the audit calendar was a hard deadline that left no slack for setbacks.

Approach

The work began with a structured stakeholder map and a gap analysis against the prior management letter. From there, a remediation roadmap was built with named owners, weekly checkpoints, and explicit escalation paths. Audit-trail requirements were documented for every key control, and program owners were paired with a designated audit-readiness liaison.

Pre-audit walkthroughs were run with the OIG team well in advance of fieldwork — surfacing issues months before they could become formal findings. Internal control testing was aligned to OMB A-123 and run on a calendared basis rather than a year-end scramble.

Outcomes

The program office completed its audit cycle without any of the prior-year findings recurring. Internal control documentation was formalized and adopted as the basis for the following year's audit-readiness work. Program leadership had visibility into audit-readiness as a managed discipline, with a sustainable cadence and trained owners — not a year-end scramble.

Context

The client was a Mid-Atlantic professional services firm whose growth had brought it across state lines without a corresponding update to its tax compliance posture. Remote employees, traveling consultants, and out-of-state client work had created income tax and sales tax nexus in jurisdictions where the firm had never registered, never filed, and — until this engagement — never measured.

The Challenge

Full back-filing exposed the firm to penalty and interest assessments that could be material to a closely-held business. Doing nothing risked discovery — and the kind of audit-driven enforcement that converts a manageable exposure into a disclosure event with real reputational and financial consequences. The board needed a recommendation that quantified the trade-offs across multiple pathways.

Approach

The work began with an activity-tracking analysis — mapping every taxable touchpoint by jurisdiction, going back to the earliest reasonable look-back period. Each state's nexus thresholds, voluntary disclosure programs, and penalty waiver provisions were researched against the firm's specific facts.

Three pathways were modeled in parallel — full back-filing, voluntary disclosure agreements (VDAs), and selective remediation — with quantified penalty and interest exposure under each. The recommended approach was presented to the board with the trade-off explicit: VDA route gave the firm the best balance of compliance, cost, and risk profile.

Outcomes

The entity was brought into compliance across the three exposure jurisdictions through negotiated VDAs, materially reducing penalty exposure relative to a discovery scenario. A forward-looking compliance posture was established with state registrations and a calendared filing process — converting tax compliance from a hidden risk into a managed line item.

Context

The client was a high-growth services company whose anticipated capital markets event required SOX compliance for the first time. Leadership had finance and operational maturity but no formalized internal controls framework, no controls testing capability, and no documentation that would withstand an external auditor's review under PCAOB standards.

The Challenge

Build SOX-compliant infrastructure in a window that left zero room for iteration. The auditor would need to rely on management's testing for the first reporting period — meaning the controls universe, the narratives, the testing program, and the supporting evidence had to all be ready before the auditor began their walkthroughs. Anything missed at this stage would surface as a material weakness later.

Approach

The framework was built from the financial statements backward — identifying significant accounts first, then mapping the business processes generating those balances, then identifying the key controls within each process. This sequencing avoided the most common SOX pitfall: documenting controls that don't actually address the financial statement risks.

Control narratives and process flows were drafted for every key control. Walkthroughs were run with control owners, who signed off on the narratives' accuracy. A testing program was built that addressed both design effectiveness and operating effectiveness, with sample sizes calibrated to the auditor's reliance threshold.

Outcomes

The framework was adopted by management as the operating model for SOX compliance. The external auditor accepted reliance on management's testing for the first reporting period — avoiding the doubled testing burden that comes with no reliance. The operationalized controls testing calendar was handed off to the internal team for ongoing operation under a sustainable cadence.

Context

The client operated multiple legal entities across two countries with intercompany activity and a manual consolidation process. Year-end close was running over thirty business days and creating downstream pressure on financial reporting, audit fieldwork, and management decision-making cadence. Investor and management pressure to accelerate the reporting cadence had become persistent.

The Challenge

The close was slow because of process design, not effort — bottlenecks accumulated at reconciliation, intercompany elimination, and consolidation handoffs. But every prior attempt to accelerate had run into the constraint that nothing could be skipped without weakening controls. The acceleration had to come from redesign, not from cutting steps.

Approach

The existing close calendar was mapped in detail, day by day, identifying which tasks ran serially that could run in parallel. The redesigned close was structured around a checkpoint model — instead of monolithic week-by-week phases, the close moved through defined gates with explicit handoff criteria.

Controls were embedded within the new flow so acceleration didn't come at the expense of reliability. Daily standup cadence during close gave leadership visibility and let exceptions surface fast enough to remediate within the window.

Outcomes

Close cycle time was reduced materially while controls held. Standardized handoffs reduced exception management and lowered the cognitive load on the controllership team. The post-close retrospective framework was adopted as a continuous improvement engine — each cycle's lessons-learned feeding the next cycle's calendar refinements.

Context

The client was an enterprise-scale organization undergoing a multi-year finance transformation spanning financial systems, operating model redesign, controls modernization, and reporting architecture. Multiple workstreams had been launched but were operating without consistent governance, status reporting, or risk management — and program leadership had limited visibility into delivery health.

The Challenge

Build PMO infrastructure that worked for both program leadership (who needed governance and reporting) and the workstream leads (who needed support without bureaucracy). Bring rigor without becoming the obstacle the workstreams worked around. Most PMO stand-ups fail at this trade-off — overshooting toward documentation theater or undershooting and providing no real visibility.

Approach

The work started with a charter library — every workstream got a clear charter with scope, milestones, dependencies, and success criteria. A RAID log structure (Risks, Assumptions, Issues, Decisions) was operated weekly, with explicit ownership for every line item.

A status reporting cadence was designed with templates that took workstream leads no more than thirty minutes to complete. An executive steering committee rhythm was stood up with consistent agenda and decision-tracking — so decisions made in the room actually got executed.

Outcomes

A mature PMO operating model was in production within six months of charter — and continued operating against its templates and cadence beyond the engagement. Two junior PMs were developed into independent workstream owners. Program leadership transitioned from reactive issue management to proactive risk and decision oversight.

Context

The client was undertaking a multi-year IT modernization with parallel workstreams: infrastructure replatforming, application migration, cybersecurity hardening, and identity-and-access overhaul. Each workstream had its own delivery team, each was tracking on its own schedule, and no one had a defensible answer to the question every executive eventually asks: are we on track.

The Challenge

Build an integrated master schedule that respected the dependencies between workstreams without becoming so complex it stopped being usable. Manage vendor relationships across multiple delivery partners. And hit contractual milestones tied to fiscal-year funding cycles — meaning slippage didn't just delay the program; it created funding-availability problems.

Approach

A single integrated master schedule was established, capturing cross-workstream dependencies as first-class objects, not afterthoughts. A vendor governance model was designed with weekly delivery reviews and monthly executive alignment.

Cybersecurity gates were embedded into the application migration path so security wasn't a separate workstream sign-off at the end. A contractual milestone tracker with proactive variance reporting gave executives the early-warning signal they needed to redirect resources before slippage compounded.

Outcomes

The modernization was delivered against contractual milestones. Sustainable IT operations were established, supported by hardened security and consolidated infrastructure. The vendor governance model was adopted as the standard for future multi-vendor programs.

Context

The client was a healthcare services organization running a portfolio of operational improvement and healthcare IT projects. Clinical staff, IT teams, and administrative leadership each had their own priorities, vocabularies, and constraints — and projects routinely stalled at the boundaries between them, with weeks lost to translation work.

The Challenge

Project leadership had to translate between clinical, IT, and administrative perspectives, all while operating inside HIPAA and HITRUST compliance frameworks that meaningfully constrained how systems could be designed, who could access what data, and how change was managed. Compliance couldn't be a sign-off step at the end — it had to be a planning input from day one.

Approach

A project intake and prioritization model was built that brought clinical, IT, and admin leadership into the same room with the same scoring rubric. Compliance representatives were embedded into each project's planning phase rather than at sign-off.

Clinical workflow analysis was standardized as a precursor to any healthcare IT change — so technology decisions started from clinical reality, not the other way around. This single change eliminated a recurring class of post-implementation rework.

Outcomes

Operational reporting visibility for clinical and admin leadership was materially improved. Clinical workflow following EHR-related initiatives ran smoother and required fewer post-implementation iterations. Compliance integration became a planning-phase discipline rather than a sign-off blocker — reducing the late-stage friction that had previously slowed delivery.

Context

The leader was a senior finance executive with responsibility for a portfolio of strategic initiatives spanning capital allocation, organizational design, and finance function modernization. The strategic agenda was clear at the top but was not consistently translating into action across the function — and the leader's calendar was being consumed by reactive issue management.

The Challenge

Chief of staff work is contextual — it's not a defined scope of deliverables, it's a question of what the leader needs and when. The role required reading the leader's intent, anticipating downstream implications, drafting on the leader's behalf, and operating across the entire function as the leader's proxy on issues that didn't require their direct attention.

Approach

Three operating rhythms were built — weekly leadership team meeting, monthly board prep cycle, and quarterly off-site planning. Drafting responsibility was taken on for executive communications, board materials, and town-hall content.

Strategic priorities were translated into operating goals with named owners, and execution was tracked. The leader's external commitments calendar and prep packets were owned end-to-end, so the leader could walk into every meeting prepared without having spent prep time themselves.

Outcomes

A sustained operating cadence was established; strategic priorities tracked and delivered. The leader's calendar shifted from reactive to strategic. The operating rhythm continued post-engagement under the team that the chief of staff role had developed — institutionalizing the cadence rather than depending on a single individual.

Context

The client was implementing an enterprise ERP platform replacing legacy general ledger, accounts payable, and fixed assets systems. The implementation team had strong technical resources but needed someone to own the finance workstream end-to-end — translating accounting requirements into system design, owning user acceptance testing, and managing the cutover.

The Challenge

ERP implementations fail at the seam between business requirements and technical configuration. Translating a chart of accounts redesign or a new approval routing rule into the ERP's configuration logic — and validating it works under realistic load — requires fluency in both accounting and the platform. Most failures trace back to that seam being owned by no one.

Approach

The work started with a requirements blueprint that documented every accounting need in business terms, then mapped each to the ERP's configuration choice. UAT scripts were built to test the requirements as accountants would actually use the system, not just functional smoke tests.

The cutover plan was designed with a parallel-run phase to validate balances before formal go-live. Hypercare was stood up with explicit triage criteria so the post-go-live period had governance, not just firefighting — a discipline that made the difference between the project being declared "done" and the operations team accepting it.

Outcomes

A successful go-live with stable operations within thirty days. The finance team operated independently on the new platform post-hypercare. Knowledge artifacts — configuration documentation, UAT library, cutover playbook — were handed off as the basis for ongoing system administration.

Context

The client operated three financial applications subject to SOC 1 reliance. Prior internal control reviews had been informal, and the upcoming SOC engagement would require documented, defensible ITGC testing across access management, change management, and computer operations — at a level of rigor the prior reviews hadn't met.

The Challenge

ITGC testing is unforgiving. Privileged access reviews that aren't actually performed quarterly, change management that bypasses production approval, computer operations failures with no follow-up — each generates a finding, and findings cluster around process gaps that look small in isolation but indicate systemic weakness when the auditor strings them together.

Approach

The test program was designed from the SOC reliance criteria backward — identifying which controls had to operate effectively for management to assert and the auditor to rely. Sampling was performed across the testing period, not just at year-end, to validate operating effectiveness over time.

On finding identification, remediation recommendations were drafted with sufficient specificity that the IT teams could execute without further interpretation. Post-remediation re-testing confirmed the gaps were closed and produced clean documentation for the auditor's review.

Outcomes

Material deficiencies in privileged access reviews and segregation of duties were identified, remediated, and cleared. Clean follow-up testing supported management's assertion and auditor reliance. The test program documentation was handed off as the operating template for ongoing internal control testing.

Context

The client's executive reporting package had grown organically into a collection of multi-tab spreadsheets owned by different functions, with manual consolidation, inconsistent definitions, and no audit trail back to the underlying GL. Each board cycle, the controllership team spent days reconciling and cleaning up — and the board still received numbers they couldn't drill into.

The Challenge

Replacing a fragmented reporting package with a single source of truth requires solving three problems at once — the data architecture (where does the data come from), the definition layer (what does each metric mean), and the visualization layer (how does it surface to executives). Skipping any of the three produces another fragmented reporting package, just in a different tool.

Approach

The work started with a metric definition workshop with finance leadership — every line item on the board package got an owner, a definition, and a source. A data model was built pulling from the GL with intermediate marts for finance-specific aggregations.

The dashboard was designed around the executive's reading order, not the data structure. Drill-through to transaction-level detail and variance commentary by business unit were embedded — so the executive could answer their own questions in the meeting rather than committing to follow-up.

Outcomes

Board-ready dashboard with drill-through capability replaced the prior multi-spreadsheet package. Reconciliation work at month-end was materially reduced. The executive team became capable of answering questions in real time during board meetings rather than committing to follow-up — a quiet but consequential shift in how board sessions ran.

Context

The client was migrating finance systems and needed the vendor master moved cleanly into the new platform. The legacy vendor master had accumulated over years of acquisitions, organic growth, and decentralized vendor onboarding. It had duplicates from typos and acquired entities, vendors with invalid tax IDs, and remittance data that didn't match current reality.

The Challenge

Migrating dirty data into a clean system reproduces the dirt — but stops in the migration timeline aren't free. The cleanse had to happen in parallel with system configuration, not as a sequential predecessor, and the final migration had to be auditable so the audit team could trace any post-migration vendor record back to its source.

Approach

Cleanse criteria were defined from the new system's data requirements, not the legacy system's tolerance. A deduplication algorithm was built with both automated matching and manual review for edge cases. Tax IDs were validated against IRS records.

Remittance data was reconciled with recent payment activity. The cutover plan included a rollback procedure in case migration validation failed — a precaution that turned out not to be needed but that gave leadership the confidence to commit to the cutover window.

Outcomes

A clean migrated vendor master in the new system. An audit-ready data dictionary handed off, documenting every transformation decision so the audit team could trace any record back to its source. Post-migration reconciliation validated balance and count integrity across the cutover.

Context

The client was a small services firm with strong commercial credentials but a near-empty federal pipeline. Leadership had committed to the federal market but had no source-to-route infrastructure, no qualified opportunities in flight, and no defensible way to evaluate which agencies and vehicles were realistic targets.

The Challenge

Federal sourcing is a discipline, not a search. SAM.gov, GSA Schedules, and agency forecasts each surface different opportunity types, on different cadences, with different qualification implications. A pipeline built from "search and bid" without qualification noise turns into a cost center; one built without sourcing breadth misses the opportunities that actually fit best.

Approach

Sourcing was established across three channels — SAM.gov for active solicitations, agency forecasts for advance visibility (often eighteen months out), and GSA Schedules for vehicle-aligned opportunities. Qualification criteria were built specific to the firm's capabilities, set-aside eligibility, and capacity.

A pipeline review cadence was designed — weekly tactical, monthly strategic — with leadership engaged in qualification decisions. This kept the pipeline reflecting an executive view of the firm's strategy, not just a researcher's list of available solicitations.

Outcomes

An established federal pipeline with qualified opportunities at every stage. A regular sourcing-to-qualification cadence operationalized with named owners. Leadership had visibility into opportunity flow and could make capacity-allocation decisions on a defensible basis — pursuing opportunities where the firm's capabilities, vehicle access, and capacity actually aligned.

Context

The client was responding to multiple state RFPs in human services and public-sector technology with overlapping submission windows. Each state had its own compliance requirements, evaluation criteria, vendor registration prerequisites, and submission protocol — and the SMEs needed for the technical content were the same people across all responses.

The Challenge

Multi-RFP response programs collapse when SMEs become the bottleneck or when compliance requirements get caught at the eleventh hour. The program needed parallel work-streams that didn't compete for the same SME hours, and a compliance review process that validated submission readiness early enough to remediate before the deadline.

Approach

Compliance matrices were built for each RFP with explicit owner assignments. A content reuse library was stood up so SME contributions to one response could be repurposed (where appropriate) for another — eliminating redundant interview cycles.

The production timeline was designed with hard internal deadlines well ahead of state submission deadlines, leaving slack for review cycles. Subject-matter experts were coordinated on a shared schedule with explicit hand-off points so no single SME became a single point of failure.

Outcomes

All submissions delivered on schedule against state deadlines. Compliance matrices cleared without remediation findings — a notable result in a multi-jurisdiction program. The content reuse library carried forward to subsequent response cycles, reducing the marginal cost of each new state pursuit.

Context

The client was pursuing federal capture in capability spaces where it had genuine technical depth but where its corporate qualifications didn't always allow it to prime. Some pursuits required set-aside-qualified primes; others required subs with adjacent capabilities the client didn't have in-house. Teaming wasn't optional — it was the access strategy.

The Challenge

Teaming partners aren't transactional. Durable relationships pay off across multiple pursuits, while transactional relationships often produce contentious work-share negotiations and post-award conflicts. Building the network meant identifying partners whose capabilities, cultures, and growth trajectories aligned with the client's — not just whoever was available for the immediate pursuit.

Approach

A partner identification framework was built starting from capability gaps and set-aside requirements, then layered with cultural and growth-trajectory filters. Candidate partners were approached with a relationship-first conversation — capability mapping and mutual qualification before any specific pursuit.

Teaming agreements were structured with clear work-share, escalation paths, and post-award governance language. Work-share was negotiated on a value-contribution basis rather than a percentage-default basis — a small change with outsized effect on post-award relationship quality.

Outcomes

A strategic teaming network supporting three competitive bid wins. Durable partner relationships sustaining capture activity beyond the initial engagement. The teaming agreement template was adopted as the firm's standard — replacing ad-hoc approaches that had previously caused work-share disputes.

Context

The client wanted to deepen relationships with three federal agencies where prior pursuits had been relationship-light — submitting strong technical proposals into procurements where the evaluator already had a strong sense of who they wanted to work with. The objective was to build durable relationships before procurements were on the table, not to influence active solicitations.

The Challenge

Government engagement has rules — pre-solicitation contact restrictions, FAR limitations on what can be discussed and when, and the appearance-of-impropriety standards that constrain how often and how aggressively a vendor can show up. The program had to deepen relationships while operating well inside those constraints. Crossing the line is worse than not engaging at all.

Approach

A stakeholder map was built of contracting officers, KOs, and program officers across the three target agencies, with engagement history and relationship status tracked for each. A structured outreach cadence was designed around legitimate touchpoints — industry days, pre-solicitation conferences, capability briefings, and educational content.

No pursuit-specific engagement happened during active procurement windows. Engagement was tracked at the relationship level, not the transaction level — the right metric for an effort whose payoff is visible only over a multi-procurement horizon.

Outcomes

Durable relationships established at all three target agencies. Capture strategy informed by direct intelligence on agency priorities, evaluation tendencies, and emerging procurement timelines. The engagement program continued post-engagement under the BD team it had been built for — institutionalizing what had begun as a directed initiative.