Bonzai’s web development turns the way your business already works into fast software: a search-ready website your own team edits, live in a week, or a custom app, CRM or client portal in 30 days, built on open source so you own every line.
Picture a typical small-business site. It was built years ago on a theme and a stack of plugins. Nobody remembers the login. Every update breaks something, so nobody updates it. It takes four seconds to load on a phone, and in those four seconds the person who searched for you has already tapped the next result.
We stopped building on WordPress in October 2026 for exactly that reason. Every plugin is code someone else wrote, on a server someone has to keep patched. We build on Next.js and Payload CMS instead: no plugin sprawl, pages that load fast, and your website and your apps in one codebase. Here is the honest trade-off: a custom stack needs a developer who knows it. That is the job we sign up for.
It is also why our builds are quick. Innovative Heating & AC got 6 service pages and 38 service-area pages, every old address redirected, in two days. CCHMG moved to a bilingual site in three. And when a spreadsheet or an off-the-shelf CRM is the real bottleneck, we build the app instead: M Cubed Technologies had a working demo of its whole workflow seven days after the project started.
Layers of a modern build. 1 Pages and search; 2 The CMS your team uses; 3 Logins, payments, signing.
7 daysTypical website launch, from the published timeline
30 daysTypical custom app, CRM or portal
YoursYou own the code; nothing to license
What you get
A site your team can edit, and an app you own
A Bonzai website is a search-ready public site your own team can edit, live in a week, with every old address redirected before launch. A custom app, CRM or client portal is the same stack, shaped around how you already work, typically in 30 days. Booking, payments and e-signing can be built in. Bilingual pages and phones are not an afterthought.
If you like how the current site looks, we can move it to this stack and keep the look pixel for pixel, then improve it over time. You are not buying a redesign you did not ask for.
Websites, live in one week, editable by your team
Custom apps and CRMs in 30 days
Client and staff portals with their own logins
Booking, payments and e-signing built in
WordPress sites moved to a modern stack, every old address redirected
Bilingual sites, and pages that work on every device
Built on open source: nothing to license, and you own it
We build for businesses in Fresno, the Central Valley and across the country that need a site their team can edit, a WordPress replacement, or a custom app, CRM or portal they own.
Owners who need a search-ready website live in a week, with every old address still working
Teams leaving WordPress or a patchwork of tools for one modern stack
Companies that need a client or staff portal, booking, payments or e-signing built in
Seven days, or thirty. 1 Map what you have; 2 Design or a working demo; 3 Build in the open; 4 Launch and hand over.
7 daysTypical website launch, from the published timeline
30 daysTypical custom app, CRM or portal
Day 3Website design is ready to review
How a build runs
Short steps, real previews, nothing hidden
You see working software early, while changes are still cheap. We start by mapping your brief, your content, and every address your old site still answers on — from its sitemap and Search Console — so nothing that ranks today gets lost.
For a website, you review the design on day 3, before it is built.
For an app, you click through a working demo in week 2.
Every change gets its own preview link before it reaches your live site, and any release can be rolled back.
At launch: every old address redirected, your data loaded, logins for your team, and a walk-through so they can edit pages themselves.
A good business website is not a brochure that happens to have a URL. It is a page people can use on the phone they already have, that your team can update without breaking the layout, and that does not throw away the addresses Google already knows.
Speed you can measure
Google’s current “good” Core Web Vitals, judged at the 75th percentile on mobile and desktop, are a Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less (web.dev, Core Web Vitals). We budget for those from the first design: images are sized, space is reserved, and scripts stay off the critical path so a mid-range phone has a chance to pass.
A good site also stays fast after the first load. App-like pages spend most of their life in clicks that do not reload the document. As of 17 November 2026, Vercel Speed Insights records LCP, INP and CLS on those soft navigations too (Vercel changelog). We treat the whole visit as the thing to measure.
Ownership and editing
Your team should be able to change a headline, a service, or a phone number without waiting on us and without dragging a layout out of shape. You should own what you pay for, on open-source software, with nothing extra to license. And on launch day, every old URL should already have a new home.
1.0s
About the limit for a person’s flow of thought to stay uninterrupted, even when they notice the delay.
Pick the path that fits the work. 1 Website; 2 Custom app or CRM; 3 Move off WordPress.
7 daysTypical website launch, from the published timeline
30 daysTypical custom app, CRM or portal
Same lookWe can keep your current design if you want it
Decision guide
A website in a week, an app in thirty, or a careful move
You do not have to buy everything at once. The right first project is the one that removes the bottleneck you actually have.
Start with a website if
People need to find you, understand the work, and get in touch or book.
Your current site is slow, hard to edit, or missing on phones.
You already have a way to manage customers, and the public site is the gap.
Start with an app, CRM or portal if
The real work lives in spreadsheets, inboxes or a tool you cannot shape.
Clients or staff need their own logins, or you need booking, payments or e-signing in the same place.
A website alone would still leave the team retyping the same record.
Move off WordPress if
Updates scare you, or a plugin break has already taken the site down.
You want the public site and the internal tools in one codebase, with previews and rollbacks.
You like the look — we can keep it — but not the server and the plugin stack underneath.
If a budget cannot cover the full request at once, we can still map the whole project and start with a launch phase. Your exact path and price come from the live estimate or a short call. We do not promise search rankings.
Where rebuilds usually slip. 1 Lost URLs; 2 Layout anyone can break; 3 Only the first load is measured.
RedirectsMap every old address before launch
FieldsLet the team edit content, not the layout
Whole visitMeasure soft navigations, not only the first document
Pitfalls
The mistakes that quietly undo a new site
A new site can look finished and still fail at the jobs that pay for it. These are the problems we plan for on purpose.
Launching without a redirect map. If a page used to answer at an old address, and that address now 404s, you have spent money to hide work you already paid to rank.
A page builder that lets anyone with a login drag the layout around. Editing should feel like filling in fields, not dismantling the design.
Judging speed only on the first document. If the rest of the visit is a web app, those later clicks need to stay in the same “good” range.
Hoping a theme plus plugins will become a product. That path is how sites get stuck on updates, and how a public site and an internal tool end up as two problems instead of one system.
Going live before the team has had a walk-through. If nobody on your side can change a page, the site starts going stale on day two.
What actually changes underneath. 1 The old stack; 2 The Bonzai stack.
Next.jsWith Payload CMS, Vercel and Neon Postgres
Open sourceNothing extra to license
RollbacksAny release can be undone
Compared
A modern stack, compared with a typical WordPress site
This is how we build, not a claim about every WordPress site. We stopped building new WordPress sites in October 2026 and move existing ones to this stack when you are ready.
A modern stack, compared with a typical WordPress site
Typical WordPress site
How Bonzai builds it
What it runs on
A PHP server and a stack of plugins
Next.js and Payload CMS, hosted on Vercel with Neon Postgres
Who can edit it
A theme or page builder that is easy to break
Your team edits fields shaped like the content, without changing the layout
Old addresses
Often left as 404s after a redesign
Every old URL is listed and redirected before launch
Typical timeline
Varies widely by theme, plugins and host
A website live in 7 days; a custom app, CRM or portal in 30 days
Who owns it
The site depends on plugins you may not control
You own what you pay for, on open-source software with nothing to license
This is how we build, not a claim about every WordPress site. We stopped building new WordPress sites in October 2026 and move existing ones to this stack.
Published ranges, then your estimate. 1 The published range; 2 Your estimate; 3 The timeline.
7 daysTypical website launch, from the published timeline
30 daysTypical custom app, CRM or portal
QuoteThe exact figure comes from an estimate or a call
Costs and timelines
What it costs on the published price table
The figures on this page are the published ranges from Bonzai’s price table, not a custom bid. Monthly care, if you want it, is a separate monthly fee. Your exact price and timeline come from the live estimate or a short call.
Typical timelines for Websites and Custom Apps
Project
Typical timeline
What shapes it
Website
1 week
Brief and content, design to review, build with redirects, live on day 7.
WordPress replacement
1 week
Your site moved to a modern stack, every old address redirected.
Custom app, CRM or portal
30 days
Map how you work, working demo in week 2, your data and logins, team using it by day 30.
The tactics below are from official pages we fetched on 22 November 2026, and from how they show up in our work. They are not a promise that every page will pass every threshold on every phone.
What current official guidance says, and how it shows up in our work. Linked to the pages we fetched on 22 November 2026.
Budget for Core Web Vitals from the first design
Google’s current “good” thresholds are LCP within 2.5 seconds, INP of 200 milliseconds or less, and CLS of 0.1 or less, judged at the 75th percentile on mobile and desktop. We size images, reserve space for media and keep scripts off the critical path so the page has a chance to pass on a mid-range phone.
Next.js now recommends Cache Components so pages can mix a static shell with request-time data. We already pre-render pages and rebuild them on a short timer, so visitors get a fast first load and your team’s edits still show up without a full redeploy.
App-like sites spend most of their life in client-side navigations. As of 17 November 2026, Vercel Speed Insights records LCP, INP and CLS on those soft navigations too. We treat the whole visit, not only the first document, as the thing to measure.
Next.js and Payload CMS, hosted on Vercel with a Neon Postgres database, plus Vercel Blob for media and Resend for email. It is the same stack this site runs on.
How fast can you build a website?
A website is typically live in one week: brief and content, a design to review on day 3, the build with redirects, and launch on day 7. Custom apps, CRMs and portals are typically in use in 30 days.
Do we own the code?
Yes. Everything is built on open-source software with nothing to license, so you own what you pay for.
Why not WordPress?
Plugins and the PHP server under them are where most WordPress sites get attacked, and they slow pages down. A modern stack removes both. The trade-off is that you rely on a developer who knows the stack instead of a plugin marketplace, and we are that developer.
Can you build a client portal or an internal tool?
Yes. Portals with their own logins, internal operations apps that replace spreadsheets or an off-the-shelf CRM, booking, payments and e-signing are all things we have built for clients.
What do you need from us before a build starts?
A brief, the content you already have, logos and any brand rules, and a list of the addresses your current site still answers on. If you have Search Console, that list is easier to complete. We can help you gather it.
Will we lose our place in Google if we move?
We list every old address and redirect it before launch, so people and search engines can still find the work. We do not promise rankings, traffic or a place in AI Overviews.
Can our team edit the site after launch without breaking the layout?
Yes. Your team edits fields shaped like the content. Changing a headline or a service should not mean dragging the design apart. We walk you through it at hand-over.
Live cards, and recent reading. 1 Related work; 2 Latest in this category.
Our workOnly live cards already on /work
MonthlyThe latest-news list is refreshed by hand
Work and what’s new
Work that already lives on this site
We only link to Our work cards that are already live, and only describe them the way that page already does. The “Latest in …” list is a curated set of recent articles, dated, with outbound links. It is checked about once a month.