Four ways to work together. Each one stands on its own, so start with the one that matches what you already know about the problem.
For when the problem is already clear and small enough to scope before you pay. One problem, one fix, finished and tested in about a week.
We agree on the problem and what finished looks like before you pay. If it turns out bigger than a fix, I stop and quote the larger piece separately.
For when something is holding growth back and you are not sure which thing it is. I look at how buyers find you, what your site and offers say, and whatever your team still does by hand. You get the diagnosis in writing and one change built inside the two weeks.
A focused fix, Start with Berg, or a bigger build can aim at any of these. None of them is priced on its own.
Positioning and direction
Who you are for, the problem you solve best, and the words that make the right buyer recognize it. I work it out from your calls, your past projects, and your customers, then put it on the pages that have to carry it.
Demand and customer experience
Search and AI-answer visibility, pages built from your own material, your Google Business Profile, and the path from a first visit to a booked call, including the forms and follow-up where interested people quietly fall away.
Products and practical systems
Calculators and assessments your buyers use, internal tools and automations that replace manual work, and prototypes that answer a question before anyone commits to a full build. I watch how people use what ships and adjust it.
When the work is bigger than two weeks, I scope it first: the problem, what finished looks like, the timeline, and the handoff. Websites, calculators, prototypes, internal tools, and the Content Engine all run this way, quoted after I have read your site and stack.
Two ways to keep going after the first project, both on a three-month first term. That is about how long steady work takes to show up in the results.
For teams with a content system already built who want it running at full speed while their own people ramp up.
For owners who want strategy and building on a steady rhythm.
I work with a small number of clients at a time, mostly asynchronously. That works when a few things are in place on your side.
Firms where the expertise is the product: consultancies, professional practices, brokerages, recruiting boutiques, and research and data companies. They have real clients and a real offer, and something in their positioning, visibility, or systems is holding growth back. Work I have shipped includes a product consultancy that needed a sharper position, a brokerage that needed to be found, and a product site at the Associated Press that needed leads. If you are pre-funding and hoping to trade equity for work, this is not a fit.
That is the normal case, and it is why Start with Berg begins with me looking rather than you choosing. Positioning, visibility, and systems problems usually show up together. My job is to tell you which one is actually costing you money right now, because fixing the third-most-expensive problem first is how a year disappears. If two are tangled together, I will say that too and quote them as one piece of work.
I tell you, before I build anything. It happens. Someone comes in certain they need content and the real issue is that the leads they already have never get followed up. You are paying me to be right about that, which sometimes means disagreeing with you. We either point the work at the thing I found, or you keep the diagnosis and we stop there.
If good work has gone nowhere, the cause is often underneath the page: crawl and indexing errors, missing schema, or two of your own pages competing for the same search. Usually the repair folds into the work already scoped. If it is big enough to need its own project, I tell you before you pay anything and price it separately.
A focused fix and Start with Berg are each paid upfront, one invoice. Larger builds split in half, one payment at kickoff and one at handoff. Ongoing work is billed monthly against a three-month first term. Anything scoped after the first project gets quoted in writing before it starts, so nothing arrives as a surprise line item.
That can work, as long as I am not the third vendor in the room negotiating with the other two. The best version is when your team or your agency handles volume and I build the system or fix the thing they cannot. The version that fails is when nobody owns the decision and I am waiting on two approvals for every change.
A few things, and the reason is the same each time: you should end up with something working. So no standalone audits, code review, or technical due diligence unless a build is attached, because a document on its own still leaves you hiring someone else to act on it. Open-ended retainers go the same way, since every month should end with finished work you can point at. Social media management, video editing, photography, and customer interviews are all better in a specialist's hands than mine, and I can usually recommend someone.
I build with Cursor and Claude Code, on Next.js and Supabase for apps, and on WordPress when that is where your site already lives. PostHog shows me how people actually use what ships, so I can improve it. For automations, I use whatever your stack will connect to.