Editorial standards
How we keep our guidance useful
What we will and will not claim, how we handle platform references, and when a page gets rewritten. Every rule below applies to the service pages on this site.
What this page covers
Written to help you decide, not to promise a result
We publish service descriptions, process explanations, and practical guidance about the platforms we work in — Wix, Squarespace, Figma, Semrush, Google Search Console, HubSpot, Slack, and FreshBooks among them. Those pages are written so a reader can make a decision about scope, effort, and fit. They are not written to sell a specific outcome, and this page sets out the rules we apply when we write and review them.
In practice that means every claim on a service page has to be traceable to something we actually do: a deliverable we hand over, a step in a documented process, or a setting someone on your side can change. If we cannot point at the work, the sentence does not go on the page.
What a service page may contain
- Scope, deliverables, and what is excluded
- The steps we run, in the order we run them
- What we need from you to start
- Platform notes and where a tool fits in a project
- Known limits, dependencies, and timing caveats
Anything outside that list — a ranking position, a lead volume, a revenue figure — is not something we can put in writing as a promise, so we do not.
No outcome guarantees
We do not promise numbers we cannot control
Search engines and advertising platforms change their rules on their own schedule. No agency controls those systems, and we will not write a page as if we did. When a service page describes an outcome, it is framed as a typical deliverable or a documented process step — never as a result you are owed.
What we write instead
A specific number of leads
The form, tracking, and follow-up steps we set up, and who answers the enquiries once they arrive.
A guaranteed search ranking
The on-page structure, page titles, and internal linking we build, plus the sections you can keep updating after launch.
A revenue result
What the site is built to do, which parts we measure, and where the numbers come from once you are live.
A fixed timeline with no dependencies
The sequence of stages, what we wait on from your side, and where a round of feedback usually moves the date.
If a sentence on one of our pages reads like a promise, treat it as a drafting error and tell us — see the corrections note further down.
How we reference tools and platforms
What a platform name means on this site
When we mention a platform, we describe what it is commonly used for and where it fits in a project. A content editor in one project may be the wrong choice in the next, so the note explains the trade-off rather than the tool's feature list.
We do not claim certifications, official partnerships, or endorsement from any tool vendor unless we hold the documentation for it. If we ever do, the document will be named on the page. A familiar logo on a service page is not evidence of a relationship, so we leave those off.
Platforms ship changes constantly. When a feature we describe changes materially, we rewrite the description instead of leaving a stale claim standing on the page — that is one of the triggers listed in the updates section below.
Reference material we actually work from: layout sheets, a staging site, and the platform documentation open in another window.
Conflict of interest
We earn revenue from client engagements, not from referrals to the tools we mention. We do not accept payment to recommend a platform, and when we have a preference, we say why.
That matters most when two platforms would both work. If the cheaper option is the better fit for your team, that is the recommendation, even when the larger build would bill more hours on our side. And if a recommendation would benefit us more than it benefits you, we will say that plainly rather than let you discover it later.
How we handle client work
No client names without written permission
We do not publish client names, logos, or detailed case studies without written permission. Where project types are described, the scenarios are composites of common engagement shapes — a small retail site, a services firm replacing a dated site, a team that needs its enquiries routed somewhere sensible — not a report on one client's results.
When a client approves a named case study, we publish it with the details they agreed to share and nothing beyond them. Until that permission exists, the work stays off this site.
Work & Case NotesWhat a case note would have to clear
-
Written approval from the client
Named in writing, with the parts they are happy to have quoted. No approval, no case note — regardless of how the project went.
-
The agreed details, and nothing more
Scope, approach, and what changed — bounded by what the client cleared. We do not fill the gaps with numbers they never approved.
-
Nothing confidential in the frame
No internal documents, customer lists, or unpublished product details — including anything visible in a screenshot.
-
A composite stays labelled as one
If a scenario is assembled from several projects to protect a client's identity, the page says so instead of implying a single engagement.
No invented testimonials or reviews
An empty testimonials section is worse than none
We do not fabricate testimonials, review quotes, star ratings, or reviewer names. If we publish a client quote in the future, it will be a real quote from a real client, with their permission and their name attached.
Until then you will not find a testimonials section on this site. A carousel of five-star cards with no verifiable source behind them tells a visitor nothing about the work — and it would contradict the rest of this page.
If we do publish one
It will carry a real name, a real role, and a project the client has already agreed to have described on this site.
Updates and corrections
When a page gets rewritten, and who to tell
We review service pages when a platform changes materially, when our own process changes, or when a reader flags something inaccurate. Those three triggers are the whole review list — there is no separate calendar that quietly ages the copy.
A platform changes
A feature we describe behaves differently, or a workflow we recommend stops working.
Our process changes
We stop doing a step, add one, or hand over a different deliverable at the end of a stage.
A reader flags it
You find a claim that is outdated or simply wrong, and you email us with the page.
If you find a claim on this site that is outdated or wrong, email [email protected] and we will look at it. Corrections are made on the page itself, not buried in a changelog nobody reads — so the next visitor sees the corrected version rather than the history.
Questions about a claim
Tell us and we will fix it
If something on this site reads as a guarantee or an exaggeration, say so. It is most likely a drafting error, and we would rather correct it than defend it.
You can reach leadership directly at [email protected], or send a note through the contact page. Either route reaches the same two people, so pick whichever is easier.
Where we are
834 W Ilex Drive, Lake Park, FL 33403, USA
Monday to Friday, 9:00 AM – 6:00 PM
Does this page cover every service you offer?
It sets the rules that apply to all of them. The individual service pages carry the scope, deliverables, and platform notes; this page is the standard those pages are written and reviewed against.
Do you ever update a page without being asked?
Yes, when a platform we describe changes materially or when our own process changes. Both are reasons to rewrite the description rather than leave an old one standing. You will not usually hear about it, but the page will say something different than it did before.
Why is there no reviews section on this site?
Because we would rather show nothing than show quotes we cannot stand behind. If a client agrees to a named quote later, it will appear with their name, their role, and the project they agreed to have described.
Can you guarantee my site will rank?
No, and no agency can. What we control is the structure, the page titles, the internal linking, and the content you can keep updating after launch. What happens in search results depends on systems we do not run.
How quickly do you reply to a correction?
We read everything sent to [email protected] during working hours, Monday to Friday. If a claim turns out to be wrong, the page gets corrected rather than annotated.
Next step
Found something that does not hold up?
Send the page and the sentence. If it reads as a promise we cannot keep, or a platform note that has aged out, we will rewrite it and the corrected version goes live on the page. If you would rather talk it through first, the contact page reaches the same inbox.