One paid week. One decision. The third step only happens if you pick me.
one paid week
no wrong answer
someone keeps it sharp
Find yours. Two of them start with the $4,500 audit. The other three are scoped projects, quoted after one call.
Prices and terms are in Engagements.
Inventory it, consolidate it, install a contribution model so it stays fixed.
Install the tooling, train the team, hand it over running.
Trust patterns, confidence states, undo, and observability, designed by someone who runs agentic tools daily.
Redesign the critical path against the outcome. Ship it. Measure it.
Rituals, handoff, QA bar, documentation. Installed in weeks, not quarters.
A drone console that runs live in the browser. A 22,000-user portal, ~40% fewer tickets. Seven brands on one token system. A one-click Figma plugin. Numbers included, misses included.
Tempering is the step that makes steel hold up under stress. TEMPER applies the same idea to an interface: ground control for one autonomous survey aircraft, designed around the minute the link drops and the battery hits reserve, not the twenty minutes when nothing happens. A self-initiated concept, built live, with simulated data.
48-hour sprint · 2026
Read the case studyA performance-marketing publisher operating 10+ owned consumer media brands had no shared styling vocabulary. Every brand's Figma kit carried its own hardcoded hexes and its own spacing improvisations, so a styling change was N hand-edits and a QA pass. I built a two-tier token architecture, then built the Figma → Claude → Figma workflow that migrated five brands in one sprint instead of five.
4 months, ongoing · 2026
Read the case studyA performance-marketing publisher's experimentation program was gated on engineering capacity: every test, however small, queued behind a build. I rebuilt an internal Figma-to-Optimizely tool from a Claude skill into a Claude Code plugin, defined the layer-naming convention that separates editable fields from structural ones, and took it through PM and engineering review as a workflow the team runs without me.
3 sprints · 2026
Read the case studyThe F1 Experiences portal showed customers a billing address and a line item reading Grandstand A75YTZ. That was the entire post-purchase experience for a $5,000 order booked nine months out. Support absorbed the gap, one ticket at a time.
2 months · 2026
Read the case studyHeures is a calendar PWA designed and built end to end. The calendar is not the interesting part. The interesting part is that every visual property resolves through a token system with zero hardcoded values, it themes across twelve accent sets and four seasonal surfaces without a single component edit, and one person shipped it using the same Claude Code and MCP stack SteelForge installs for clients.
Ongoing · 2026
Read the case studyA free-forever Figma plugin that generates full 50–950 Tailwind color scales from any hex and exports them as Figma variables, Tailwind config, CSS custom properties, or JSON. Live on Figma Community, installable in one click.
Open on Figma CommunityShipped, maintained · 2026
Read the case studyDrop in an image, get the art back. Runs in the browser, built on this site, free to use.
Tool · Live
Open itPick by budget and appetite. Not sure? The audit converts into either of the other two.
$4,500
one-time
Start here. Most people do.
$6,500
per month
The audit's roadmap, owned by me.
Fixed bid
quoted after one call
Net-new surfaces, bigger swings, or plain product design.
Andy Ramos. Senior product designer, Charlotte.
First-call objections, answered first. Missing one? Ask it in the form.
Audit: $4,500 flat. Retainer: $6,500 a month, three-month minimum. Projects: fixed bid after one call. No discovery fee, no rate card behind a form.
No. You own the findings and roadmap on final payment. At the walkthrough I’ll offer to own the P0 list. Say no on the same call and nothing changes.
One 45-minute call a week, Monday, Wednesday, or Friday. A written update every Friday. You’re buying output on a schedule, not a seat in your standup.
Then it’s a different engagement, and I’ll say so. The retainer is about one day a week. If you need four, you need an employee, and I’ll help you write the job spec.
No. Hourly pays me more for being slow. The monthly rate reserves the capacity. Out-of-scope work gets a written change order before it starts.
No. The reserved day a week is the product. Said at signing, not in month two.
Rolling monthly after a three-month floor. From then on, pause anytime and the month stops with you; 30 days’ notice to end it. Three months is the floor because a system doesn’t visibly move in four weeks. If it isn’t working, end it.
You do, on payment. That includes tooling: plugins, MCP servers, Claude Code workflows. They keep running if we stop. I keep case-study rights only to what you approve.
Andy Ramos. One person, no account layer, no subs. Two retainers plus about one audit a quarter is the whole business.
Audits kick off on a Monday and deliver five business days later. You get a real date, not a range. Nothing is promised on a Tuesday or Thursday.
Both, surgically. The AI Workflow Audit ends with a tool running in your stack. Production builds hand off to your engineers, in a language they respect.
When the real gap is headcount. No amount of design fixes that. Everything else, ask.
Most start with the $4,500 audit. Retainer slot or project instead? Say so in the last field. One form, one reply.
From me, not a sequence. If it is not a fit, you hear that first.
Price, scope, delivery date. In writing, before anything starts.
The only meeting an audit needs. The rest is written and async.
Pre-product, or the real gap is headcount? Say that too. I’d rather tell you an audit would come back thin than sell you one.
hello@steelforge.design — if you prefer email.
