The queue
Small fixes wait behind big projects, often until they no longer matter.
Your Webflow site, rebuilt and run from Slack.
Ask in 
Slack to edit a page, build a new one or check your 
analytics.
Every change arrives as a 
preview and goes live when you approve it.
Maya asks NewBase in Slack to change the homepage headline. NewBase replies with a preview link; the preview shows the new headline “Every load, accounted for.” highlighted, and Maya approves it. It goes live.
Maya asks NewBase for a page for the Q4 carrier webinar. The preview shows a new page in your brand with a signup form; she approves.
Maya asks which pages lost traffic last week. NewBase answers in the thread: visits were down 18%; /pricing −31%, /product/loads −22%, /blog/carrier-comparison-guide −17%, /careers −9%.
Maya asks NewBase to publish a Google Doc as a blog post. The preview shows the post with a cover image, meta description and alt text added; she approves.
A small change shouldn’t take the long way around.
The ceiling
Site builders make the first page easy. The custom parts get harder each time.
The blind spot
How's a page doing? The answer lives in three tools, so the question waits.
Read every change
before it goes live.
Every request comes back as a change you can read line by line, already checked. Publish it, send it back, or undo it later.
Work
Inbox 4History
Waiting on youChange the homepage headline2 min ago
London event page, Berlin layout1 h ago
Rename Shipment Hub everywhere3 h ago
Fix 2 broken links on /pricingToday
Work › Home page
Ask for the change.
Say it the way you’d tell a colleague.
Change the homepage headline to “Every shipment, accounted for.”
NewBase is preparing a preview
Work › Home page
Change the homepage headline
Ready for review · Maya Chen · 2 min ago
Maya asked“Change the homepage headline to ‘Every shipment, accounted for.’”
Hero headingFreight, all in one place.Every shipment, accounted for.Page titleFreight managementEvery shipment, accounted for
All 4 checks passed
- AskedMaya Chen · 9:41
- Planned and draftedNewBase · 9:42
- Your reviewWaiting on Dana
- Live on your siteAbout 2 minutes after you publish
Open previewRequest changes
Live on your siteEvery shipment,
Every shipment,
accounted for.
Track every load, invoice and carrier in one place.
See how it worksConsole checks your site while you sleep.
Every night it scans each page for broken links, missing alt text and empty meta descriptions. By morning, the fixes are waiting for your review.
2 broken links7 images without alt text1 missing meta description
Last scan 2:00 AM · 48 pages · 4 fixes ready
- 1/pricing · broken link
- 1/careers · broken link
- 7/blog/peak-season · alt text
- 1/about · meta description
Built from your
brand system,
not a blank page.
New work is assembled from what you already have: your components, your past pages, your voice rules and your colors. Each draft says what it used.
Component library
Freight ForumTwo days on freightEventHero
AJS Ana, Jonas and Sam
SpeakerRow
Work email Register
SignupForm
Tone of voice
- Plain over clever. “Ships Tuesday”, not “Lightning-fast delivery”.
- Numbers, not adjectives. “Two days, 40 talks”, not “a packed programme”.
- No exclamation marks. “Registration is open.”, not “Register now!”
Past page
Freight Forum Berlin12–13 November · Berlin
/events/berlin
Colors and type
Ink #14213DGreen #2F6F62Amber #E8A04BPaper #F4F1EA
Aa
Author for headlines
Geist for body text
Tokens from the codebase
The draft: London event page
Cairn Events
Two days on freight, carriers and the Q4 peak.
Freight Forum London. Talks from the people who plan the peak.
Register AJS
Waiting for Dana to approve
Built from
- EventHero
- SignupForm
- Layout of /events/berlin
- Tone: numbers, not adjectives
- Ink + Amber
Move your site over,
one signed-off phase at a time.
Typically 4–6 weeks. The dates go in the plan you sign in week 1, and each stage ends with something you check.
Audit
- URL inventory and redirect map
- Content model draft
- List of integrations and custom code
You sign off on
The migration plan and redirect policy
Rebuild
- Components in your repo
- Sanity schemas and Studio
- One finished page to approve
You sign off on
One finished page, before the rest
Migrate
- Posts, assets and forms moved
- Redirects tested against the inventory
- Every page checked against the old site
You sign off on
Your content, checked against the old site
Hand over
- Accounts transferred to you
- Runbook and editor training
- 30 days of hypercare
You sign off on
The handover, with training done
Before you book a call.
If your question isn’t here, bring it to the conversation.
Can anything go live without our approval?
No. Every change waits on a preview until someone you’ve named approves it, in Slack or in the Console. Anything published stays in History and can be undone in one click.
Is NewBase an AI website builder?
NewBase works with your site’s components, content and brand rules. Requests come back as changes for your team to review.
Do our editors lose the CMS?
No. Your editors keep editing text, photos and menus in Sanity Studio. The code, content and hosting accounts are in your name, and the handover includes the repository, a runbook and editor training.
Do we need to use AI to maintain our site?
No. Every page’s content lives in Sanity, so your team can edit text, images and SEO fields in Sanity Studio like any CMS, with no AI involved. Adding a new kind of page or layout takes a developer, either yours or me. The AI agents in Slack are there when you want them, never required.
Will moving our site hurt search rankings?
I inventory URLs, plan redirects and check the moved pages against your existing site. A migration cannot guarantee search rankings.
How long does a migration take, and what does it cost?
A typical migration takes 4 to 6 weeks and starts at $5,000, scoped and priced once before work begins, with 30 days of post-launch hypercare included. Afterwards, you can run the site yourself, use the NewBase Agent for $1,000 a month, or join the Partner Program for $3,500 a month with human QA on every deploy and one active engineering request at a time. See migration pricing.
Should my site be Astro or Next.js?
Astro if every visitor sees the same pages. Next.js if the site has logins, reads live product data or shares React components with your app. I build both, and the first call usually settles which.
Your next website change starts with one message.
Tell us about your site and the requests that keep piling up. We’ll tell you honestly whether this way of working fits.
Book a conversation