Website development, answered.

It depends on what the site has to do: how many products and sizes it carries, whether it takes retail orders, wholesale requests or both, which tools it connects to, and who writes the content. There is no published price. Every project is quoted in writing after we read your brief; what drives the cost explains each factor.

The scope, the timeline and the price, in writing. Your proposal also lists what is quoted or handled separately, so nothing is decided by accident. Scope, timeline and pricing then go into a service agreement that both sides sign before work starts.

Payment processing approval, which is the provider's decision, product photography, laboratory testing and the reports themselves, and the monthly developer plan if you want it. Processor fees are set by the processor in its own agreement. Your proposal lists each one.

Launch with the products you sell now rather than every product you might add, and start with a wholesale request flow if most of your orders are wholesale. Supply your own photos and reports organised by product, size and lot, and give one person the authority to approve designs and copy so feedback arrives in one round.

Send a brief: two taps and your details, submitted on the page. A project lead replies with a quote and a timeline, in writing. You can also message us on WhatsApp or email support@vantalabsresearch.com.

Most sites are fully built and live within 72 hours to a week. A large catalog, custom features or a buyer portal take longer, and your quote states the timeline before you commit.

Things outside the code: copy and photos that arrive late, rounds of feedback spread over weeks, or a decision about how you sell left until after design. Payment processor approval runs on its own timeline, so it is worth applying early.

You send a brief and a project lead follows up to plan the build. We design the site and you sign off on every page before it is coded. Our developers then hand-code it, load the catalog and documents, connect payments and email, and test every page, form and checkout path on phones and desktop before launch.

Your logo and colours, a product list with the sizes you sell, your reports or wherever they currently live, your policies, and your domain login. Most of all we need to know how you sell: retail checkout, wholesale quoting or both. If pieces are missing, we can write the copy, design a brand and launch with a partial catalog.

Yes. Our work shows live research-supply stores our team designed and hand-coded, including Vanta Labs and Genesis Biomapping. The Vanta Labs case study is our own store, labelled as ours rather than a client project.

A custom design and hand-written code, the catalog, product pages and documentation pages, a checkout or wholesale request flow, research-use-only copy and an access gate, and search setup: titles, structured data and a sitemap. Every page is tested on phones and desktop before launch.

We hand-code sites in Next.js and React, the stack Vanta Labs and this site run on, with no themes, page-builder templates or AI-generated filler. If you are set on Shopify, WordPress or another hosted platform, say so in the brief and we will tell you honestly whether we are the right fit; Shopify vs. custom compares the two.

Yes. Products, sizes and reports are modelled as linked records, so each size links to its own report and a new report appears on the product page and in the COA library at once. The library can be searched by product, batch or lot number.

Yes. A retail store with listed prices can sit beside wholesale quantity pricing or a request form, and a buyer portal with accounts, quotes and reorders can be added when wholesale grows. See B2B buyer portals.

Yes. We review the current site first and tell you whether to rebuild or improve what is there. Products, sizes, documents and, where your platform allows an export, customers and orders move across, with a tested redirect map; see redesign and migration.

You do. Your domain, content, code and site are yours, it is written into your agreement before we start, and it all stays yours if you stop the monthly plan.

Yes. The code is handed over along with your domain, hosting and analytics, all in your name. You can add products, change prices and edit pages yourself after launch.

Yes. A service agreement sets out the scope, timeline and pricing, signed by both parties before work starts, and every price is confirmed in writing on quotes and invoices. We sign an NDA when you want one.

Admin or API access to the services being connected, set up with our own login where the provider allows it. That way you can remove our access at any time without changing your own.

No. We build the site and write copy to strict research-use-only rules, but what your business may sell, how your terms are worded and what you owe are questions for your own lawyer and accountant.

Yes. We scope the merchant application alongside the build, so the site and the application describe the same business, then connect the approved account to a mobile-first checkout for cards, Apple Pay and Google Pay. Every merchant account is subject to the processor's approval; see payment processing.

A second processor connected to the same checkout and left switched off. If the first account is closed or goes down, changing over is a setting someone flips, not a new website, and you keep taking orders on the same site.

No. Custom code does not change whether a provider approves your business; approval is the provider's decision either way. Underwriting reads the site, and claim-laden copy is a reason applications get declined, so we review your checkout, product pages and research-use-only copy before it does.

Connecting a processor is part of the build. The processor's own fees, approval and payout terms are separate, set by the processor and written into your agreement with them.

Where your store and processor allow it, a follow-up text and email goes out for a card that declined and for a cart that was filled and left, linking back to the same cart.

Yes, from the first page rather than retrofitted: clean titles and descriptions, structured data, a sitemap, and an llms.txt, a plain text file that points AI tools at the pages and facts that matter. Speed, titles, structured data and the sitemap are checked before launch.

SEO makes the site fast, crawlable and rankable on Google. AEO, answer engine optimisation, writes so a direct question gets a direct answer a featured snippet or AI Overview can lift. GEO, generative engine optimisation, makes the business easy for ChatGPT, Gemini, Perplexity and AI Overviews to find, understand and name; SEO vs. GEO goes further.

No. Google and the AI tools decide what they show, and nobody can insert a brand into a model's answer. We do the work that gives you the best chance and show you what changed.

The build includes the technical basics, and the monthly developer plan includes monthly search and AI-search improvements. SEO and AI search is the full ongoing service, with an audit, new pages, listings and a plain-words monthly report, and it is quoted on its own.

We work to keep them. Pages that rank keep their URL wherever possible, every changed URL gets a one-hop permanent redirect to its real equivalent, and after launch we submit the new sitemap and watch for crawl errors. No one can promise a ranking will hold, but nothing is redirected to the homepage by default.

Research-supply brands only: peptide stores, wholesale suppliers, and brands we stock, label and ship for. Every site is built around a research catalog, COA pages and research-use-only copy.

The same rules this site runs on: research use only, with no usage, dosing, reconstitution, effect or outcome claim on any page. No purity figure appears unless it is printed on a published report for that product and size, and you approve every word.

No, for any search term, however much volume it has. Where published literature exists we write cited summaries that state the finding as the abstract does, name the model and link the paper, the way our research pages do.

A notice visitors confirm before they browse, stating that the materials are for research use only. Vanta Labs uses a research-use and 21+ gate; we build the one your site needs and keep research-use-only wording on product pages and at checkout.

Only what is documented. Purity appears as printed on a published report, never as a blanket figure, and certifications appear only where the business has documented them. Testimonials and reviews must be real, permissioned and compliant; we will not invent them. See research-use-only storefront copy.

We connect your domain and set up hosting and analytics as part of the build, with the accounts in your name. On the monthly plan our team runs them for you; off it, they are yours to run.

We hand-code sites to load fast on every phone and check speed before launch. Speed also depends on what is added later and how the site is maintained; Core Web Vitals explained covers how it is measured.

Sites are hand-coded and checked before launch, including forms, redirects and error pages. On the monthly plan, speed, security and uptime are watched and updates are applied to keep the site secure, so most problems are found and fixed before a customer notices.

Every page on phones, tablets and desktop browsers, test orders through each payment method and shipping rule, every email the store sends, speed and search setup, and forms, redirects and error pages.

We build and test the new site separately, then switch at a quiet time with the old one kept ready. Any downtime is planned and kept short, and orders, forms and emails are checked within the first hour.

A monthly plan that gives you a developer team on call 24/7 for your site: fixes, changes, updates, new pages and features, plus speed, security and uptime. You message the team and it gets done; see maintenance and support.

Through one thread to the team, not a ticket queue. Tell us what you need in plain words and we confirm what will change and when.

New pages, features and integrations are part of the plan. Something the size of a new build is quoted separately, and your agreement says where that line is.

No. The plan is optional and quoted on its own. Your site, domain, content and code stay yours whether you keep it or stop it.

Yes, after a review of the site, so we know what we are taking on. If the platform makes something impossible, we will say so plainly.