Second Chance Opportunities, LLC is me, Jim Hancock. I build the systems businesses actually run on — data pipelines, brokerage and accounting integrations, internal tools — and I operate a systematic trading platform of my own.
Moving data between systems that were never meant to meet, and into somewhere you can query it. Brokerage, banking and accounting APIs; vendor feeds; warehouses that keep the original payload rather than only what was parsed from it.
Schwab, Interactive Brokers, QuickBooks Online.
The software a business runs on and never shows anyone. Admin tools, review and approval workflows, dashboards over live data. Built to be operated rather than demonstrated, which mostly means handling the cases a demo skips.
Including the one my own trading runs on.
The spreadsheet somebody reopens every Monday. Recurring imports, reconciliation, reports retyped from one system into another — turned into something that runs without you and says so clearly when it has not.
Starting with my own accounting.
Every key, secret and OAuth token is held in a managed parameter store and read at run time. Nothing is hardcoded, committed to a repository, or left sitting in an environment variable. A stale credential served quietly is worse than no credential at all, so there is no local fallback to serve one.
Automated analysis produces confident, plausible, wrong answers — a summary that contradicts the table printed directly beneath it. Every number in a document I hand over is checked against its own evidence before it is sent.
This page has no framework, no build step and no third-party request: even the fonts are served from this domain. The same preference runs through everything I build. Fewer dependencies mean fewer ways to fail quietly.
Second Chance is one person, on purpose. The person who designs a system is the person who operates it at two in the morning, which is a durable incentive to build it plainly and leave it documented. You will not be handed to anyone else, and nothing gets lost between a salesperson and whoever ends up doing the work.
What I build sets out the work in detail, and systems shows four of my own. The company page carries the entity detail an API provider or counterparty normally asks for.