Gonzalez Global

Studio Log // Positioning a Project Build

When taking on new client engagements, the way you frame the scope dictates your leverage for the rest of the project.

Here are 3 positioning rules we follow at Gonzalez Global:

1. Diagnose Pre-Purchase Friction Most agencies jump straight into fixing whatever the client asks for. We look one layer above that: where are their buyers getting stuck before making a purchase decision? Positioning your work around pre-purchase friction transforms you from a commodity developer into a strategic partner.

2. Pitch the Outcome, Not the Labor Clients do not buy hours, they buy certainty. When pitching a technical restructuring, we show them a live proof-of-concept preview of the finished state. Showing a prospect their own product line restructured gives them total clarity and removes the risk from the decision.

3. Package as a Fixed Build, Not a Retainer Open-ended retainers often lead to scope creep and client fatigue. Packaging the solution as a fixed-tier project delivered over 2 to 3 weeks sets clear boundaries, protects studio bandwidth, and ensures cash flow stays predictable.

Writing this from the gate, about to board a flight to Chicago, then head to NYC a week after.

Let this be a quick reminder: the whole purpose of building an online business is freedom.

MRR is cool yeah. But what's the point of escaping the corporate 9-to-5 only to build a self made prison where you become a slave to constant client messages and endless business worry. Kinda defeats the whole purpose.

The timeline for magic is decades, not days.

Enjoy the week family.

Why we write scopes of work in HTML (and compile them to PDF)

If you want to charge premium rates for standard projects, you cannot send unstyled Word documents or generic templates. Your scoping document is the first real indicator of the design standards you will bring to the build.

At Gonzalez Global, we write our proposals in clean HTML and compile them using a custom Node.js script and Puppeteer. We treated the document like a physical print asset:

• Intentional Typography: Instead of accepting default AI outputs, we pair Cormorant Garamond for editorial headers, Space Mono for technical metadata, and Inter for body legibility.

• Tactile Paper Tone: Setting the background to a warm off-white (#FAFAF5) so the proposal feels like a physical print specimen instead of a harsh digital screen.

• Dynamic Pagination: Using Paged.js CSS rules to enforce dynamic page breaks, cover pages, and automated footer page numbers.

It compiles directly to your desktop in seconds. If you want the HTML source template and the compilation script to use for your own client pitches, drop a comment below and I will send the files over to your DMs.

Someone asked me this week why I don't run this like a course. Modules, calls, a cohort.

Because the accountability thread isn't what's missing for most people. The spec is.

You already know how to build. What's missing is the documentation, the pricing, the positioning, the first client sequence.

That's the whole bet behind everything in here.

Just wrapped a full rebuild of a desert real estate concept site. Eight listings, full asset library, zero stock photography.

The instinct with AI tools is to move fast and skip the boring part. Structure first, content second, polish last.

Every build that's actually converted for me went the opposite direction. Structure, then restraint, then one deliberate detail that makes it feel expensive.

Speed is not the edge anymore. Everyone has speed. Discernment is the only differentiator left.

Talked to three freelancers this month who all had the same problem. They all know how to build. They have no idea what to charge.

Most people set a price based on what feels comfortable to ask for, not what the math actually requires. That's how you end up profitable on paper and broke in your bank account.

I dropped a calculator sheet in the resources that starts from your actual monthly survival number and works backward to a floor rate.

No guessing involved.

Spent this week refining the exact prompt structure I use for every GG build.

Most people write a website prompt like they're ordering on DoorDash. Vague ask, generic result, then they wonder why it looks like every other AI-generated site.

The brief has to carry brand voice, layout logic, and constraint before Antigravity ever touches it. Otherwise you're not directing the model, you're just hoping it knows itself.