Everbase for B2B SaaS
Your product moves fast. Your website should too.
Give your marketing team a clear path from a campaign idea to an on-brand page. I rebuild your site, then help you keep improving it through previews, approvals and ongoing support.
The problem
Where SaaS marketing sites get stuck.
-
01
Product releases outpace the site.
An integration ships and the integrations page still lists last quarter's. One template each for product, integration and use-case pages keeps the explanation in a content model, so adding one is an entry rather than a build.
-
02
Campaigns wait behind development work.
The event is booked before the page is. Pages composed from approved sections, with a bounded path from request to preview, take the coordination out of the routine ones. A section that does not exist yet is still a code change, and I will say so when you ask for one.
-
03
Buyers want proof before a demo.
Buyers evaluate on their own first, so case studies, comparison pages and educational content have to be easy to find and easy to keep current. I build the structure for them. The stories and the numbers have to come from your customers.
A worked example
What one request looks like.
Illustrative The request, pages and details are made up to show the steps. None of it is client work or real data.
-
Make a London event page using the Berlin layout.
-
Start from the Berlin page, change the event details and add nothing new.
-
A preview URL shows the page before anything is public.
- Source
- /events/berlin/
- Selected
- Event details
- City, dates, venue, speakers
- Changed
- Brand components
- Hero, agenda, speaker grid
- Kept
- Form destination
- Same form and CRM destination, London campaign value
- Confirm
-
Someone on your side approves this exact version. Nothing is published before that, and a later edit needs a new approval.
-
The release record names what went live.
- URL
- /events/london/
- New
- Changes
- One new page, no existing page edited
-
Form activity on the new page first. Qualified outcomes only where CRM attribution can support them.
Scope
What the engagement includes.
The foundation
A fixed-price rebuild of the site you have, with 30 days of hypercare after launch.
- Product and use-case pages
- Event and campaign pages
- Comparison-page structure
- Customer story template
- Content model in Sanity
- Redirects for every URL that changes
- Key form handoffs, checked at the CRM
- Defined analytics checks
Ongoing improvements
Optional and monthly. Pause or cancel any month.
- New campaign and event pages from approved sections
- Content and page updates, previewed before they go live
- Template and integration changes, one active request at a time on the Partner Program
Not included
Named here so nobody finds out later.
- Experimental testing, scoped separately
- A redesign or new copy, scoped separately
- Brand identity, which I do not do
- Changes inside the product, which stay with your engineers
Process
How it works.
-
Understand
I list the page systems, forms and publishers, and separate templates from one-offs. Forty integration pages from one model move differently from forty built by hand.
-
Build
Product, integration and use-case pages get one template each, and existing pages move as content. The sections your team composes from are agreed before the build.
-
Launch
Changed URLs get one redirect to the final address. Forms are tested at the CRM record with attribution intact, not at the success message.
-
Improve
Campaign requests go through preview and approval. The measures are approved-request-to-release time and campaign readiness, plus qualified demo submissions once their definition and attribution are verified.
A marketing page does not fix product churn, so I do not measure one against it.
Tools and handoffs
Where the marketing site stops.
Where the line usually falls
Astro
The marketing site
- Pages, and the components behind them
- The content model, and who can publish to it
- URLs, metadata and the structure under them
- Experiments on the marketing pages
The handoff
Signup, and what follows
- Form to record
- Campaign attribution
- Analytics events
- Route into auth
Your product
The application
- Login and account data
- Billing, plans and entitlements
- Provisioning
- Anything reading live data
The tools it hands off to.
Questions
Questions from B2B SaaS teams.
Can we keep HubSpot and our current CRM?
Usually, yes. The forms and attribution are rebuilt against the new site and tested at the destination: the record that lands in the CRM with its campaign fields intact, not the success message in the browser. If something was quietly broken before the move, this is usually where it shows up.
How are pages approved?
You review each change at a preview URL. Who can approve is agreed at the start, and nothing is published until that person approves the exact version they saw. A later edit needs a new approval.
Can we migrate without changing URLs?
Yes, where the current URLs are worth keeping. Any URL that has to change gets one redirect straight to its final address, with no chains, and the map is tested against the real inventory before launch.
Who edits product content?
Your marketing team, in Sanity, within the fields and sections agreed for the site. Engineering keeps the components and templates. A new kind of section is a code change, which is the trade for a site that stays on brand.
What is included in ongoing support?
It is optional and monthly, and you can pause or cancel any month. The monthly options cover requests through preview and approval and, on the Partner Program, human QA on every deploy and one active engineering request at a time. I am one person: if I am unavailable, the work waits.
Do you design the site too?
I design pages and sections from the brand you already have. I do not create brand identity, and a redesign or new copy is scoped separately from the fixed migration price.
Get a site assessment.
Send the site URL and what is slowing your marketing team down.
I will reply by email with the next step. It may be a migration, a scoped improvement or a reason to keep the site where it is.