Accepting new engagements

Independent model audits for decisions that must survive scrutiny.

We reproduce backtests, test forecasting and risk models, and deliver the findings memo, reproducible notebook, and remediation path your team can inspect.

Start with the decision, the model, and what must hold up under review. Scope and fee are agreed in writing before work begins.

StatGazer / public sample work product Ref. SAMPLE-001

Illustrative · synthetic data · not a track record

Sample deliverable

Model & Backtest Audit — Findings Memo

A deliberately flawed synthetic strategy is rebuilt on point-in-time inputs so the decision-maker can see what survives.

Reported versus reproduced metrics — illustrative synthetic data, not a track record
MetricReportedReproduced
Sharpe (annualized)1.80.7
Annual return14%6%
Max drawdown−9%−21%
Hit rate58%52%
High

Look-ahead in the signal pipelineA feature was joined on report date instead of its as-available date.

Excerpt from the public synthetic sample. Read the complete memo ↗
  • NDA before confidential data
  • Direct founder delivery
  • Reproducible handoff
Evgenii Azarov, founder of StatGazer

Founder-led review

Evgenii Azarov

Founder · Data scientist · Financial engineer · Your direct reviewer from scoping through handoff

Inspect the full credibility ledger →
  • Econometrics · statistics · ML · financial engineering
  • PhD in Law · 2012 · finance training at NYU
  • 20 years private teaching & consulting · New York · global

01section Work product

Inspect the working standard before sharing data.

The product is the evidence trail: a findings memo that states what changed, a reproducible notebook for the calculations it contains, and a remediation path your team can act on. Client work stays confidential; the memo sample and notebook below are separate synthetic examples of the deliverable standard, not client results.

Code-rendered synthetic companionRNG_SEED 20260609
Code-rendered synthetic companion comparing an invalid future-dependent signal with a point-in-time-safe signal. The future-dependent curve rises implausibly while the safe reconstruction falls and experiences deeper drawdown.
Illustrative · synthetic data · rendered by the repository script with RNG_SEED 20260609.This companion reimplements the public notebook's leakage check as a chart; it is separate from the memo figures, not a notebook output, client data, or a track record.Open full-size chart ↗
sample-audit-notebook.ipynbsynthetic sample
# randomness is explicit
RNG_SEED = 20260609

df["momentum_20"] = (
  df["asset_ret"]
  .rolling(20).mean().shift(1)
)

# finding: future data enters here
df["leaking_future_mean_5"] = (
  df["asset_ret"]
  .shift(-1).rolling(5).mean()
)

The full public notebook records its seed, data-generating process, leakage check, walk-forward split, and findings.

Finding excerptSynthetic sample
Confirmed · high

Future information enters the feature set.

Evidence: the feature contract marks the input unavailable at trade time.

Action: remove it, rebuild on point-in-time inputs, and rerun the full validation path.

02section Engagements

Start with the decision at risk.

Choose the smallest review or build that can answer the question. The model audit is the flagship path; adjacent work uses the same evidence standard.

03section Review path

The review leaves a record, not just a verdict.

Each checkpoint produces something your team can inspect, challenge, and keep. No unexplained score and no junior handoff between the question and the answer.

  1. S.01

    Scope the decision

    Define the model, data, decision, constraints, and what must be defensible to the reviewer who matters.

    Written scope + evidence plan
  2. S.02

    Reproduce the result

    Rebuild the path from raw or minimally processed inputs where access allows, making timing, assumptions, exclusions, and manual steps explicit.

    Reproduction notebook
  3. S.03

    Challenge what survives

    Test leakage, regimes, out-of-sample behavior, uncertainty, monitoring needs, and remaining limitations.

    Findings memo + remediation
  4. S.04

    Hand over the evidence

    Walk your team through the code, conclusions, limits, and the triggers that should prompt another review.

    Code + report + handoff

Data handling

NDA-first, minimal extracts where possible, founder-only access unless agreed otherwise, and no third-party AI training on client data.

Ownership

You own the agreed deliverables. The engagement agreement states ownership and license terms; the written scope records access requirements, deliverables, timing, and fee before work starts.

Professional boundary

Technical model review and research consulting — not a financial-statement audit, regulatory assurance, investment, legal, or tax opinion.

04section Practical details

The questions procurement and internal champions ask first.

If your process needs a different NDA, onboarding packet, or review boundary, raise it during scoping.

How is confidential data handled, and will you sign an NDA?

Yes. We sign an NDA before reviewing confidential data and are glad to work under yours. Where possible we work inside your environment or on a minimal extract. Access is founder-only unless otherwise agreed, and we do not use client data for third-party AI training.

Who owns the deliverables and the IP?

You own the deliverables produced for the engagement, including agreed code, models, notebooks, and reports. We retain pre-existing methods, tooling, and general know-how. The engagement agreement states the exact ownership and license terms.

How are scope, fee, and timing set?

Productized engagements may publish a fixed fee for a defined scope. Custom work is priced after scoping: a fixed fee where work is well-defined, or a written rate and estimate where open-ended. No work starts, and no fee is charged, outside an agreed written scope. Timing is set by the published product scope or the custom written scope.

Why use an outside reviewer instead of the internal team?

An outside reviewer gives the internal champion a defensible second read from someone who did not build the original model. Your team keeps ownership and context; StatGazer adds a reproduction record, findings memo, and remediation trail that can travel to an IC, risk committee, or vendor review.

Is this a financial audit or regulatory assurance service?

No. StatGazer provides technical model review, validation, research, and engineering consulting. It is not a CPA firm, broker-dealer, investment adviser, or regulatory assurance provider, and its deliverables are not financial-statement audit opinions or regulatory assurance reports.

05section Next step

Start with the model and the decision it supports.

Send a high-level description without confidential data. We will tell you the shortest honest path to an answer and whether StatGazer is the right reviewer.

Replies within 24 hours · Direct founder line hello@statgazer.com

Send a project brief