Next.js development
Next.js sites that work like a product
For sites with logins, live data or code shared with your React app, plus a CMS to publish from.
- Happy Travels
- Son Of Earth Northern Rivers NSW
- Konpak Tiny Homes Australia
- Brookfarm Byron Bay
- Moonshine Coffee Byron Bay
- Find Creatives
- Jase Sullivan Interior Design
- Klammer
- Flim video productions
- Caffesso Gourmet Coffee
- AUNA
- NEST Apartments




Why Next.js
Next.js is worth it once the site needs logins, live data or components shared with your product. If yours is a plain marketing site, I'll point you to Astro instead.


















Is Next.js right for you?
Next.js pays off for some sites, not all of them.
It's worth the extra code once the site has to do things, not just show things. This is how I decide.
- Best for
- Teams who already know wp-admin, or rely on its plugins
- Who edits pages
- Your team, in wp-admin with Gutenberg or Bricks
- Starting price
- From $8,000
- Time to launch
- 4 weeks
- Upkeep
- Core, theme and plugin updates to keep on top of
- Logic and data
- Forms and plugins
- Hosting
- Managed WordPress hosting
- Best for
- Marketing sites, blogs and docs where every visitor sees the same pages
- Who edits pages
- Your team, in Sanity or Payload with a live preview
- Starting price
- From $12,000
- Time to launch
- 4 to 6 weeks
- Upkeep
- Static pages, so there's almost nothing to patch
- Logic and data
- Forms and APIs; logged-in areas move to Next.js
- Hosting
- Vercel or Cloudflare, in your account
- Best for
- Brands selling products online, with checkout and payments handled by Shopify
- Who edits pages
- Your team, in the Shopify admin, with sections set up for the pages you change most
- Starting price
- From $12,000
- Time to launch
- 5 to 8 weeks
- Upkeep
- Shopify looks after the platform; the app list stays short so the store stays quick
- Logic and data
- Products, checkout and payments run on Shopify; apps and integrations cover the rest
- Hosting
- Hosted by Shopify, on a monthly Shopify plan billed by Shopify
- Best for
- Sites with logged-in areas, dashboards or code shared with a React product
- Who edits pages
- Your team, in Sanity or Payload; app screens change with the code
- Starting price
- From $12,000
- Time to launch
- 4 to 8 weeks
- Upkeep
- Package updates, plus any server code it runs
- Logic and data
- Sign-in, payments, APIs and server routes, with Supabase or Convex
- Hosting
- Vercel or Cloudflare, in your account
| Compared on | WordPress | Astro | Shopify | Next.js |
|---|---|---|---|---|
| Best for | Teams who already know wp-admin, or rely on its plugins | Marketing sites, blogs and docs where every visitor sees the same pages | Brands selling products online, with checkout and payments handled by Shopify | Sites with logged-in areas, dashboards or code shared with a React product |
| Who edits pages | Your team, in wp-admin with Gutenberg or Bricks | Your team, in Sanity or Payload with a live preview | Your team, in the Shopify admin, with sections set up for the pages you change most | Your team, in Sanity or Payload; app screens change with the code |
| Starting price | From $8,000 | From $12,000 | From $12,000 | From $12,000 |
| Time to launch | 4 weeks | 4 to 6 weeks | 5 to 8 weeks | 4 to 8 weeks |
| Upkeep | Core, theme and plugin updates to keep on top of | Static pages, so there's almost nothing to patch | Shopify looks after the platform; the app list stays short so the store stays quick | Package updates, plus any server code it runs |
| Logic and data | Forms and plugins | Forms and APIs; logged-in areas move to Next.js | Products, checkout and payments run on Shopify; apps and integrations cover the rest | Sign-in, payments, APIs and server routes, with Supabase or Convex |
| Hosting | Managed WordPress hosting | Vercel or Cloudflare, in your account | Hosted by Shopify, on a monthly Shopify plan billed by Shopify | Vercel or Cloudflare, in your account |
Not sure which fits? Tell me about your project and I'll recommend one.
The process
Most Next.js builds take 4 to 8 weeks.
Longer when there are a lot of integrations. You get a preview link to click through at every stage.
- PlanWeek 1
Plan the build
- Project scope
- Page map
- Integration plan
- Fixed price and dates
- DesignWeeks 1 to 2
Design
- Key screens
- Reusable components
- Empty, loading and error states
- Your sign-off
- PagesWeeks 2 to 4
Pages and screens
- Next.js app
- React components
- Shared styles
- Preview links
- DataWeeks 3 to 6
Data, logins and integrations
- Sign-in and roles
- API connections
- CMS connected
- Database set up
- LaunchWeeks 6 to 8
Testing and launch
- Testing
- Speed checks
- Launch
- Handover notes
Case study
A marketplace built on Next.js.
Find Creatives connects creative professionals with the businesses hiring them.
Next.js and Supabase
Find Creatives
A marketplace web app built end to end: listings, profiles, search and a jobs board, with accounts and an admin area behind it.
Next.js
Listings, profiles, search and a jobs board
Supabase
Accounts, database and admin behind it
The problem
Creatives and the businesses hiring them had no single place to find each other, so the work happened across scattered directories and inboxes.
What I built
A full marketplace: listings, profiles, search and a jobs board, with accounts and an admin area, from the data model to launch.


What you get
A site with product features, in code you own.
A Next.js build on your own hosting, with a CMS your team can use and written notes any developer can follow.
Logged-in areas
Dashboards and data
Headless CMS
APIs and integrations
Speed and SEO
Easy to hand over
Testimonials
What clients say about working with me
Tools
The tools around a Next.js build.
Next.js and React at the core, plus the data, CMS and hosting your product needs.
Framework
- Next.js
- React
- TypeScript
- Tailwind CSS
Data and auth
- Supabase
- Postgres
- Stripe
- REST and GraphQL APIs
Content and hosting
- Sanity
- Payload
- Vercel
- Cloudflare
Workflow
- Figma
- Claude Code
- GitHub
- Sentry
Related services
Is the site only part of it?
Most Next.js builds sit beside a product, an app or a launch. I build those too, so you keep one person across all of it.
FAQs
Next.js questions, answered
When do I need Next.js instead of Astro or WordPress?
When the site has to do more than show pages: logged-in areas, dashboards, calculators, deep integrations, or content that changes per user. If Astro or WordPress covers what you need, I'll say so.
Which CMS do you use?
Usually Sanity or Payload. Sanity if you'd like it hosted for you; Payload if you'd rather keep everything on your own hosting and database, since it runs inside the Next.js app. I set it up around your content and connect publishing to the site.
Can my marketing team still edit the site?
Yes. Your team publishes in the CMS and the site updates, usually without a rebuild. They can check a live preview before anything goes out.
Do you build the backend too?
Yes. I connect the site to sign-in, databases, payments and outside services, and build the product logic behind them. For heavy backend systems I work alongside your engineers.
Can you work in our existing codebase?
Yes. I review what's there first, agree with you what to keep and what to rebuild, and follow your conventions and review process.
Where is it hosted?
Usually Vercel or Cloudflare, in your own account. You own the code and the hosting, not me.
What does it cost?
Next.js sites start from $12,000 and usually take 4 to 8 weeks. Platforms with a lot of integrations are scoped from your brief. Either way you get a fixed price before anything starts.
What do I get at the end?
A working site or platform in code you own, on your hosting, with a CMS, written notes and a handover call. I also fix anything that comes up in the 30 days after launch.
Available for projects
Let's work together
Have a project in mind? I'd love to hear about it. Let's get it built together.
hello@talkk.com.au

