A specialist practice in development, technical SEO, AI search, and AI consulting. For companies, and for agencies.
Chapter I
If you run a company
You already have a site, customers, and a team with more work than hours. You want one specialist who can:
If you run an agency
You have clients, a reputation, and more briefs than bench. You want a specialist who:
Same practice, same standard of work. The only thing that changes is whose name is on it.
Chapter II
Build
Sites built to be run by the people who own them, on the platform that fits the business rather than the one that is fashionable.
Platforms: WordPress, Shopify, and custom CMS builds when the content model needs one.
Be found
The part of SEO that lives in the code: how search engines crawl, render, and understand a site, and what stops them.
Be cited
Generative engine optimization: making a business legible to AI assistants and AI search, so it is found, described accurately, and cited.
Run lighter
Automations and agent-based operating systems for real work, introduced one painful task at a time instead of as a platform you have to adopt all at once.
That order is the method. The next chapter shows it.
Chapter III
Most AI projects start with a product. This one starts with your week.
Every engagement, in this order
Engagement file
Illustrative example. Not a client record.
Notes from the first conversation.
This is the pain. Fix it first.
Automate intake before anything else.
Today, by hand
After
One intake flow reads the form and the inboxes, creates the CRM record, routes it by a written rule, and sends the acknowledgement. A person reviews only the exceptions.
Built in your accounts. Your team can see every step.
What to do next, in order.
| When | What | Why now |
|---|---|---|
| Next | An agent drafts first replies for a person to approve | Requests are structured now, so replies can be too |
| Then | A weekly pipeline brief, written from the CRM | The data is clean enough to summarize |
| Later | Connect billing and onboarding | Only after the first two hold up in daily use |
| Not yet | A customer-facing chatbot | Nobody asked for it, and it adds risk |
Saying "not yet" is part of the job.
Scope: the Next and Then items above.
Price: written for this scope, after the recommendation is agreed. There is no package.
Approve to start
Your file starts from your situation, not from this example. The first step is the same for everyone: describe it.
Chapter IV
Chapter V
There are no case studies here yet.
Client work is published only when the client approves it, and agency work stays with the agency. Nothing has been approved for publication, so this ledger is empty rather than filled with examples nobody signed off.
If you want to see how the practice works before you commit, ask. A walkthrough in conversation is the honest substitute.
| Client | Discipline | Published |
|---|---|---|
Chapter VI
RP&Co is led by Renan Pellegrinelli, who does the work. The person who scopes a project is the person who builds it, audits it, or automates it, so nothing is lost between a sales call and delivery.
The practice works in English, with companies and agencies in the United States first.
Chapter VII
What you run, what slows it down, and what you have already tried. Expect questions back, not a pitch.