Ninety courses. Six benches.

Interfaces, not hours of 'coding.' You will describe an engagement as an outcome a buyer can recognize, and notice when you are selling time instead.

• Describe an offer as an outcome, not a pile of tasks
• Tell a frontend engagement from a generalist one
• Say no to work that is not the offer

Pages, states, and the things that are out. You will write a scope a client can disagree with before the work begins, which is the point.

• List the screens and states that are in scope
• Write exclusions a client can see
• Spot a request that changes the scope

Before this: What a Studio Sells

Weeks, risk, and the cost of revisions. You will put a price next to a scope and be able to say what would change it.

• Price from a written scope
• Name the risk that moved the number
• Change the price when the scope changes

Before this: Scoping an Engagement

A beginner pass at a statement of work for a frontend engagement: deliverables, assumptions, and a definition of done a designer and a client can both read.

• Write deliverables a client can check
• List the assumptions the price depends on
• Define done without a vague 'polish' line

Before this: Scoping an Engagement

A standing review, a short agenda, and notes that say what changed. You will stop collecting feedback in three chat threads.

• Run a review with an agenda
• Write down the decision, not only the comment
• Park feedback that is a new scope

Before this: A Statement of Work

A brief, access, review, and the work you still own. Hiring here means a contractor on a scoped interface, not building a department.

• Brief a contractor with the scope, not a vibe
• Review their interface work against that brief
• Keep client decisions in one place

Before this: The Weekly Client Review

Members, liability, and the difference between you and the company, taught with a frontend studio as the example. This is education for people who build interfaces. It is not legal, tax, or accounting advice, and it is not a substitute for a Missouri attorney or a CPA.

• Explain what an LLC separates from its members
• Name what forming one does not do by itself
• List the questions to take to an attorney before you file

Before this: What a Studio Sells

Ownership, votes, and what happens if a member leaves, walked through on a short agreement for a studio. This is education for people who build interfaces. It is not legal, tax, or accounting advice, and it is not a substitute for a Missouri attorney or a CPA.

• Find who owns what in an operating agreement
• Find how a decision gets made
• List the clauses you would ask a lawyer to explain

Before this: An LLC, in Plain Language

Assignment, license, and the portfolio exception, read as part of a client contract. This is education for people who build interfaces. It is not legal, tax, or accounting advice, and it is not a substitute for a Missouri attorney or a CPA.

• Tell an assignment from a license
• Find the clause that transfers the interface
• Ask for a portfolio right before the work starts

Before this: A Statement of Work

Deposits, milestones, and a simple set of books for a studio LLC. Advanced only because the habits are exact. This is education for people who build interfaces. It is not legal, tax, or accounting advice, and it is not a substitute for a Missouri attorney or a CPA.

• Invoice from the company, not from a personal note
• Tie a payment to a milestone in the scope
• Keep a record you could hand to a bookkeeper

Before this: Pricing Frontend Work

A tech lead's week on a small frontend team. Critique, sequencing, and the call that is still yours when the group disagrees.

• Split an interface across three people without collisions
• Run a critique that changes the work
• Name the decision you are not delegating

Before this: Your First Contractor

Ranges, unknowns, and the update you send when the range was wrong. The estimate is a communication, not a promise you whisper.

• Give a range and the assumption under it
• Surface an unknown before it becomes a slip
• Update the estimate in writing when the assumption breaks

Before this: Pricing Frontend Work

Interface critique, a written note, and a follow-up that checks the change landed. Eleven weeks of making review a practice instead of a performance.

• Run a critique with a question, not a tour
• Write the change you expect to see
• Check that the change landed

Before this: The Weekly Client Review

Roles, a second lead, and the client relationship that still sits with the company. Twelve weeks on growing past the founder without pretending you are a large firm.

• Name the work that should leave your desk
• Hand a client relationship to the company, not to chaos
• Write a role before you hire for a vibe

Before this: Leading a Frontend Trio

You will leave with an offer, a sample scope, a price, a list of operating-agreement questions, and a checklist of what you will not decide alone. This is education for people who build interfaces. It is not legal, tax, or accounting advice, and it is not a substitute for a Missouri attorney or a CPA.

• Write the offer the studio will sell
• Attach a scope and a price to that offer
• List the formation questions you will take to a lawyer

Before this: An LLC, in Plain Language