Refract Group2026
Next.js and Nuxt development
A custom website, designed and built by one team.
We design and build websites as custom code, in Next.js or Nuxt, and hand over a repository your company owns. They start from $15,000 and usually take four to eight weeks to build. This site is one: it runs on Nuxt, hosted on Vercel.
When custom code is the right choice
A custom website is written by developers in a framework, where a visual builder has you assemble pages in its editor. We prefer to build this way, in Next.js or Nuxt, and work on other platforms when one suits you better. Our studio is in Sydney, Australia, and we work between Sydney and New York with startups and technical companies.
The site shares parts or logins with your product, your engineers will own it, or it has to do something no visual builder can.
Marketers will publish every week with no developer to call on, or a few pages have to be live very soon. A builder suits both better.
Content can live in the code, as it does on this site, or in a CMS your team edits. Which one is agreed before the price.
The code, the hosting and the documentation belong to your company and sit in its accounts.
In short
What you get
A website designed and built by the same people, delivered as code in a repository your company owns. With it come the design system, notes on running and changing the site, and a CMS if one was in scope.
What it costs
Websites start from $15,000, with scope and price settled first. A CMS, integrations and content carried over from an old site add to the figure. A first week of work is $2,500, which comes off the build if it follows within 60 days.
How long it takes
Most of our website builds take four to eight weeks. A CMS, a login shared with your product or a lot of existing content puts a build at the longer end.
When it’s not a fit
Your marketers publish every week and have no developer to call on. The site is a few pages that must be live very soon. Or nobody will maintain code once we hand it over. A visual builder suits all three better.
How a custom build runs
Framer and custom code comparedChoose the platform
Four questions come first: who edits the site, how much gets published, what it plugs into and when it has to launch. If a builder fits those answers better, we say so.
Agree the editing
We list what your team must change without a developer. That decides whether a CMS is part of the build, before the work is priced.
Design the system
Pages are designed as a set of components on your own content, so the design file and the code describe the same parts.
Build it
The people who designed the site write it, in a repository under your account, so you can see what changed and why.
Launch and hand over
We check redirects, titles and forms, then document how the site is run. Your engineers take it from there, or we look after it.
Where to go from here
Questions about a custom build
Use the one your engineers already work in, because they will keep the site after handover. If nobody on your side has a preference, we choose and explain why before the build starts. We build in both, and this website runs on Nuxt.
Only for some sites. Custom code is the better choice when the site shares logins or parts with your product, when engineers will own it, or when it must do something a builder cannot. Webflow or Framer is the better choice when marketers publish often with no developer nearby. Our comparison pages set each pair side by side.
Yes, if a CMS is part of the build, and that is agreed before the work is priced. Without one, the content lives in the code and a change goes through a developer, as it does on this website. Tell us what your marketers need to change and how often.
It is hosted in an account your company owns, on the host your engineers prefer. This website is hosted on Vercel. After launch a coded site needs a developer for changes beyond content, so decide early who that is. Your engineers can take it over with our documentation, or we can look after it.
You own all of it. At the end you have the live site, its code in your repository, the design files and written notes on how to run and change it. It is built to be handed over, so another team could pick it up.
No platform ranks a page. Rankings follow the page: whether a search engine can reach it, what it says and whether it answers what someone searched for. On a coded site the titles, the sitemap and the redirects are part of the code, so we include that work in the build and check it at launch.
Websites start from $15,000. The price depends on the page types, whether a CMS is included, what the site connects to and how much content moves from an old site, and it is agreed before the build starts. A first piece of work is one week for $2,500, which comes off the build when it starts within 60 days.
Most of our website builds are done in four to eight weeks. A custom build runs longer when a CMS has to be set up, when the site shares a login with your product, or when a lot of content has to be moved. We agree the timeline before work starts.
We need to know who will edit the site and who will maintain the code after launch, because both shape the build. We also need access to the accounts the site will live in, the content, and one person who signs off pages. If your engineers have their own review process, we work inside it.
Yes. Our studio is in Sydney, and a custom website in Next.js or Nuxt is the kind we prefer to build and put our name to. The example we can point to is this website, which we designed and built ourselves. It runs on Nuxt, is hosted on Vercel and keeps its content in the code.
A closer look at the work
- How to explain a technical product on your websiteLead with the problem and who has it, in your buyer’s words. Then layer the depth: a plain claim, the proof under it, and the specification one click away.
- What makes a good landing page?A useful landing page continues the promise that brought someone there, explains the offer, supports it with evidence and makes the next step clear.
- How to get your company cited by ChatGPT and AI searchNobody can guarantee an AI citation. You raise the odds with pages that answer questions directly, crawlers let in, and one consistent description of you.
Does the website have to do more than a builder allows?
Tell us what the site has to do and who will look after it once it is live.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch