NickOS
Say or type anything and it is routed into tasks, projects, events and ideas. Built on Next.js, Supabase and the Anthropic API.
Self-taught builder with 10+ years inside SaaS, fintech and regulated markets. I design, build and ship custom tools with the Anthropic API, Next.js and Supabase, and I stress test AI output until it holds up. Years on the business side mean I start from what a team actually needs, not from the tech.
Tools I’ve designed, built and run myself, from voice capture to automated daily briefs to offline phone apps.
Say or type anything and it is routed into tasks, projects, events and ideas. Built on Next.js, Supabase and the Anthropic API.
One sheet tracks every project, deadline and open loop, and an automated daily brief pulls in the day's calendar and new email so the next step is always clear.
A hub of small web apps that install like native apps and keep working with no signal: an HTML editor, an audio converter, and Night Cruiser, a generative driving radio with recorded instruments.
Reads a website’s HTML, sitemap, metadata, speed scores, calls to action and lead capture, then outputs a ranked fix list with an implementation and QA plan. First run: WCTC.
What I notice when I push on AI systems, written up.
A curated critical edition of 20 AI reasoning traces from a single conversation under scrutiny. Under pressure, the model produces a self-shaped explanation for what it said, and that explanation becomes material for its next answer. Edited as artifacts, not as evidence of a hidden mind.
Contract and part-time work. Remote, based in Phoenix.
One tool or workflow, scoped with you, built and handed over in about two weeks. Internal dashboards, intake flows, capture tools, automated briefs and reports.
Connecting an LLM to the tools a team already uses, like Gmail, Calendar, Sheets and a database, so routine work runs itself and a person only checks the result.
Stress testing AI features and model output: finding where answers go wrong, contradict themselves or drift, and writing up exactly what failed and how to fix it.
Keeping a tool running after launch, with small changes as the team’s needs shift.
Before building full time I spent a decade in B2B growth and content. It’s why the tools I build start from the business problem.
Owned the marketing function across B2B and B2C at an early-stage fintech, spanning brand, GTM, acquisition, lifecycle, content, partner growth, analytics, and conversion.
Built and ran a vertical B2B content program for a regulated cannabis marketplace, translating research, product information, and market complexity into useful content for buyers, customers, and sales teams.
Journalism, then B2B content and growth leadership, now building.
Learn something complex quickly → find where it breaks → build the fix → make sure it holds.
The same pattern runs through SaaS, MarTech, regulated cannabis, fintech, education, and the tools I build now.Have a tool you need built, a workflow that should run itself, or an AI feature you need tested?
Email me with what you’re trying to do and I’ll tell you honestly whether I can build it and how long it would take.