You keep your own practice and 70% of the fee, and the Sean Dinwiddie’s Webmastery name brings in local clients. Joining the team asks one thing, quality work; no fee, course or purchase stands in the way. Webmasters join at every stage of the craft, junior included, and joining begins with the work itself, the first job paid like every other.
Every job has a written scope and is reviewed against it before it goes live, and the name vouches for the result. The review checks results, never how the work was done; on a custom app, its passing scenarios are part of the result. One feature, scope to launch shows one such review, line by line; the review is also where what one job teaches becomes the team’s.
70% of the fee on your work
You work as a subcontractor from your own practice and keep 70% of the fee on your work. The agency keeps 30%, inside the published fee, never added to the owner’s bill.
The 30% pays for the name, the contract, billing and collection, and the review before launch; each job comes with a written subcontract naming your fee and the date it is paid. An addition the client asks for is quoted in writing before it starts and paid like the rest of the job, so no addition is unpaid work.
The clients you bring in stay yours, and so do your outside clients. Bringing one under the name is your choice; while an agency contract runs, its work is billed through the agency.
What the 70% comes to
Your 70% comes from the fees on the client work you deliver, never from recruiting or memberships.
For example, say you build and hand over a family shop’s website as a one-time job at a full share ($6,000). Your 70% is $4,200, and the agency keeps $1,800. When an owner holds the monthly engagement with you as their webmaster, your 70% is $4,200 each month it runs. The smallest job the team takes is a third share ($2,000), and 70% of it is $1,400.
The ladder
The ladder runs from junior to mid to senior. Webmasters move up on delivered, reviewed results, and any rung takes any job. The split is the same at every rung and on every job run through the agency, one-time or held each month, whoever brought it in.
What a rung changes is the peer review before Sean’s: a junior’s launch gets a senior’s review, a mid’s gets a mid’s or a senior’s, and seniors review others’ work; then Sean reviews every launch against the written scope. A peer review is paid work, from the agency’s 30%, never from the 70% of the webmaster whose launch it is. Those reviews are how the ladder teaches: what a senior has learned reaches a junior’s work before it launches.
Your name on your work
You show your work under your own name, credited “for Sean Dinwiddie’s Webmastery”, and look after the sites you build for as long as the owner holds the monthly engagement and wants you.
Sean covers the work when you are away. If you leave the team, a running engagement stays with Sean Dinwiddie’s Webmastery until it ends. Either way, the fee follows the work: the 70% of a month someone else delivers goes to them, or to the agency when Sean covers it.
What the team brings
Joining the team comes with the Sean Dinwiddie’s Webmastery name, local work, a published fee that is never lowered to win a job, and a written scope for every job, so the time on each job goes to the craft rather than to selling and haggling. Work reaches you two ways: the clients you bring in under the name, and inquiries Sean refers by a written rule to a webmaster whose craft fits the job and who has room for it. Owners speak with Sean; you draft the scope on the agency’s template, Sean confirms the fee, and each written scope names the webmaster on the job. You can turn down any job.
Every job serves the team’s mission, strengthening the service industry of Jefferson State, one handover at a time.
The team’s course teaches the practice from the first user story to the API behind it, and on to agents and small language models. What one webmaster learns on a job becomes the team’s, through the reviews before every launch and the lessons, revised as the practice improves, so webmasters grow faster than they could alone.
The stack follows the project: many brochure sites run on WordPress, set to update themselves, while custom apps follow the chain the course teaches, from Gherkin scenarios through Redux Toolkit to a Haskell (Servant) API on Postgres. The team also builds in Rust, and in Python or Go where a project calls for them. Each written scope names the stack.
Webmasters on the team belong to the online country club through the quality of their work, and reach its library and discussions with no membership tier. Members meet at meetups such as the KFalls AI Meetup, where the community’s talks on business automation and the AI protocol ecosystem were given, bring their questions to one another and learn from each other’s work.
How to join
Call (530) 638-3238 or email hello@seandinwiddie.com with a link to work you’ve built (a live site or a repository) and the kind of job you want, from a WordPress brochure site to a custom app. Sean answers every serious inquiry, one that includes both, and joining begins with the work itself.