← Back to Blog
ProcessConsulting

From Figma to Deployed: How an Engagement Runs

Patrick "Wiloak" Wilson · November 10, 2026 · 5 min read

Most agency engagements fail in the gap between the demo and production. The mockup looks great. Then it sits in a branch for three months while scope creeps and the invoice grows.

We run differently. Fixed price, fixed scope, and a deploy date you can put on a calendar. Here is what actually happens between the first call and the moment your code is live.

Week zero: the call and the scope

Everything starts with a 30-minute call. No deck, no discovery retainer.

You tell us what you want built. We tell you which SKU fits and what it costs. A Web App is fixed-price, somewhere in a known band, on a 3-to-5-month clock. See pricing for the exact ranges.

The output of this call is a one-page scope. It lists what ships, what does not, and the deploy target. We both sign it. The price does not move after that unless you add scope in writing.

This is the most important step. A vague scope is how a $10K build becomes a $40K argument. We name the boundary up front so neither of us pretends later.

Week one: design and the data model

We start with the Figma and the schema at the same time.

The design is not decoration. It forces the real questions early. What does the empty state look like. What happens when the list has 10,000 rows. What does the error toast say.

While the screens take shape, we model the data. Tables, indexes, access patterns. For a DynamoDB-backed app that means deciding partition keys before you write a single Lambda. Get this wrong and you pay for it every week the app is alive.

You see both by end of week one. Clickable Figma, written schema. If something is off, this is the cheap moment to catch it.

Week two onward: the build

Now we wire the thing together. Frontend, API, storage, auth.

We deploy to a staging environment on day one of this phase, not at the end. Every push goes live to a URL you can click. You are not waiting for a big reveal. You are watching the app fill in.

Infrastructure is code from the start. No console clicking, no snowflake servers. The whole stack is in a repo, which means it rebuilds from scratch and you can read exactly what runs in your account.

This is where ex-AWS experience earns its keep. Right-sizing compute, picking the cheaper managed service, not over-provisioning a database for traffic you do not have. Most AWS bills hide savings nobody is tracking. We try not to write that waste into yours in the first place.

The handover: you own the code

When the scope is built, we ship it to your account and hand you the keys.

You own the code. The repo, the infrastructure definitions, the deploy scripts. Not a license, not a seat, not a hostage situation. If you never talk to us again, the app keeps running and any engineer can read it.

We exit clean. That is the deal on every engagement. A 2-person team cannot afford to babysit dozens of accounts, so we build things that do not need babysitting. That constraint is why we shipped 17 production products, 10 of them in our first 7 months.

The handover includes a short runbook. How to deploy, where the logs are, what to do when something breaks. Plain text, not a 40-page wiki nobody reads.

What this looks like in practice

The pattern scales down and up. A Cloud Bill Audit is a tighter loop. We read your account, find the waste, hand you a list. A RAG Chatbot or an OpenClaw install follows the same arc with a different shape.

The point is the same every time. Fixed price, a clock, code you own, a clean exit.

One build we did was a support agent, now running in production. That did not come from a longer engagement. It came from a tight scope and a real deploy.

Why fixed price changes the work

Hourly billing rewards slow work. Fixed price rewards shipping.

When the number is locked, our incentive is to finish well and exit. Yours is to get a working app on a date you can plan around. Those incentives point the same direction, which is rare in this business.

If that sounds like the way you want to build, the first step is the same 30-minute call. We will tell you the SKU, the band, and the deploy date. Book a free 30-minute call and we will scope it on the spot.

Further reading

Want to Talk About Your Project?

We write about what we do every day. If any of this resonates, let's chat.

Request a free 30-min call See services and prices