Company & valuation models
Forecasts, DCFs, comparables, and sensitivity analysis with assumptions you can follow.
AVAILABLE FOR FREELANCE PROJECTS
I’m Zane. I research markets, build the tools to test my ideas, and follow the numbers back to their source. Now I’m bringing that same hands-on approach to freelance financial work.
01 / ZTrader
ZTrader is my personal market research and trading platform. It connects data collection, strategy testing, execution, and the accounting that checks the results.
Building it has meant working through the whole problem: the model, the data underneath it, and what actually happens when an idea meets a market.
02 / FIELD NOTES
Four problems. Four better questions.
Notes from the ZTrader work. These are the moments where finding the mistake was more useful than finding a good result.
A row in the log looked like a win that should have been a loss. The row turned out to be correct, but chasing it exposed a bigger problem. The system decided whether a trade had won by comparing its own copy of the price candles, while the market settles on its own published result. The two disagreed often enough to matter. My code also scored an exact tie as a loss, where the market’s rules resolve a tie as a win.
I switched settlement to the market’s official winner, kept the candle comparison only as a fallback, and wrote a backfill that re-checked every historical row. Of 4,923 rows, 551 had the wrong outcome, roughly one in nine. Twenty-one belonged to longer-horizon markets that hadn’t resolved yet and were left open.
LessonA backtest is only as good as its definition of a win. Every P&L figure I had produced before this was suspect until it was recomputed against the source of truth.
The strategy log said I was up by several times what was actually in the wallet. The log recorded orders when they were placed, and some were never filled. It also knew nothing about earlier losses. I stopped treating the log as the record of what happened.
Real P&L is now the live wallet balance minus a stored baseline, shown next to the log’s figure so any gap is visible at once. Underneath sits a daily ledger built from an append-only transaction file: every buy, payout and fee, with a running balance. Building it turned up two things. The exchange’s events arrive slightly out of order, so balances have to be computed in file order, not timestamp order. And my own first version anchored to a start timestamp that was off by a year, which counted every historical fill as new and sent the running balance deeply negative. I caught it because the running balance was plainly impossible.
LessonReconcile to the one number you can’t argue with, which is the balance held by the custodian. When the model and the balance disagree, the model is wrong.
Two live strategies won 90% or more of their trades and still finished negative. Their paper-trading twins, running the same logic, looked solidly profitable. The gap was about three to four percent of notional per trade, and it broke into three parts: the taker fee (around 0.8% at those prices), a slippage buffer on fill-or-kill orders (around 2.3%), and adverse selection, because the orders that fill are disproportionately the ones the market was about to move against.
When contracts are bought near 0.90, the break-even win rate is about 90%, so a few points of friction consume the whole edge. Paper trading had been filling at the quoted ask with none of those costs. I added baseline strategies, which buy a fixed side on every bar, to measure what it costs just to play. That toll came to one to three cents per trade at the ask, and every taker strategy has to clear it before it earns anything.
LessonA simulated result isn’t evidence until the fill model is at least as pessimistic as the real order book.
In the same audit, a control strategy that bought “down” on every bitcoin bar made money over the two-week window. It had no signal at all. Bitcoin had simply drifted down.
That changed how I read every other winner. A strategy whose gains resemble a short position in the asset may be carrying market exposure and not producing anything of its own. The audit’s rule is that before a winner is promoted, its returns get regressed against the market move using the factor-exposure module I built into the backend, and only what’s left over counts.
LessonEvery result needs a control that shows what doing nothing clever would have earned.
Research and engineering case studies. Historical examples describe process, not expected trading performance.
02 / The Assumption Desk
Five views of one connected company model, not five separate calculators. Revenue growth, margin, and tax carry across every tab, so a change on one view shows up on the others. Pick one above the exhibit and change the sliders to see the five-year build respond.
INTERACTIVE EXHIBIT / NOT A CLIENT MODEL
Revenue compounds a starting revenue at a growth rate set on the Revenue or Margin tab. Margin applies an operating margin to that same revenue to get EBIT. EPS divides a starting net income, grown at that same rate, by diluted shares. FCFF taxes a starting EBIT at 25% and nets out a reinvestment rate, where reinvestment is (CapEx − D&A + increase in operating working capital) ÷ after-tax operating profit — not capex alone. DCF discounts five years of cash flow, off its own $10m starting FCFF assumption, plus a 2.5%-growth terminal value, at WACC.
Every figure is illustrative and describes one hypothetical company, not a real filing. This simplified set omits full operating schedules and debt-to-equity adjustments. Reset restores every tab to its default at once.
03 / The Approach
INTERACTIVE EXHIBIT / FICTIONAL COMPANY DATA, READ-ONLY
04 / Working Together
Forecasts, DCFs, comparables, and sensitivity analysis with assumptions you can follow.
Backtesting, market research, return attribution, and portfolio diagnostics.
Repeatable data workflows, internal dashboards, and reports that reconcile to their source.
LET’S BUILD SOMETHING USEFUL
Tell me what the model is for, who will use it, and when you need it. That’s a good place to start.
zanedhanoo@icloud.com+1 (868) 275-6342
Revisit the work ↑