Reason 01
You need the build, not a full-time hire.
One senior engineer, about a decade behind the work, on one invoice. Stop after the first sprint.
File · DEV-2026/Engineering
Next.js 16·Payload·Railway·Neon·Performance·Migrations
Web development by one senior. The repo stays yours.
One senior engineer with about a decade builds it, signs it, and ships nothing until two QA passes clear.
- 01One senior engineer, named on day one
- 02Repo in your GitHub org
- 03Two QA passes before ship
- 04Free build audit in 4 business days
You own the repo · Reply within 1 business day
~/dev-2026/audit
$ grovant audit --site=your.site --priority=p0
→ ok · queued · eta 4 biz days
Free build audit
Form 01 / 02Send the site. Get the scorecard.
Send your site or repo. A Lighthouse run, a full audit, a plan, and a price in 4 business days. No call needed.
bash · 80×24senior · standing by
Reply within 1 business day · Read by a senior
Build manifest · sample format
The scorecard you see every week.
Our web development services come with proof you can read. Every deploy logs a Lighthouse run against the public Core Web Vitals thresholds. You see the same scorecard your engineer sees, in the repo, not a PDF you wait a week for.
Live client build · prod
Lighthouse · mobile · 75th percentile
Measured against the public CWV thresholds- LCPThreshold
≤ 2.5s
Public Core Web Vitals standard
Largest Contentful Paint
- INPThreshold
≤ 200ms
Public Core Web Vitals standard
Interaction to Next Paint
- CLSThreshold
≤ 0.10
Public Core Web Vitals standard
Cumulative Layout Shift
- TTFBThreshold
≤ 800ms
Public Core Web Vitals standard
Time to First Byte
Deploy log · sample format
Repo in your org- (sample)feat(home): hero rebuild, slow interactions fixedmain → production
- (sample)perf: defer non-critical scriptsmain → production
- (sample)feat(cms): Payload upgrade, new adminfeat/payload → preview
- (sample)fix(ssr): cache miss on /pricing, load time droppedmain → production
This is your weekly review. No PDFs. The repo is the report.
Run my Lighthouse auditBuild audit · sample findings format
What you learn before you commit a dollar.
The free audit starts every engagement. The failures become your first sprint.
Audit card · sample of the full findings format
Delivered to your inbox- FAILSlow interactions on mobileA form tap blocks the page past the 200ms bar. Users feel it.
- FAILPage weightThe homepage ships more than it needs. Unused code slows first paint.
- WARNType safetyAPI routes are not typed, so bugs slip through.
- WARNShip checksNo preview link, no speed gate, no type check before live.
- PASSSearch markupClean. Schema on every template, sitemap builds itself.
- PASSRepo hygieneMain branch protected, reviews required, secrets kept out.
The full audit lands in your inbox in 4 business days, free.
Get my free build auditWhat you get, in four numbers04 / 04
I·Every build
2 QA
passes before ship
II·A senior replies
1
business day
III·Site to audit
4
business days
IV·On your build
~10 yrs
per senior
You own every file · Month to month · One named senior
grovant.config.ts · how the build holds up
One file. The whole stack you own.
The same stack runs marketing sites and web app development, frontend to backend: Next.js, Payload, Postgres, all open source and self-hostable. No proprietary CMS, no license bill, no lock-in. Any senior can pick it up from the repo in your org.
Sections · 04 · entries · 16
grovant.config.tspackage.jsontsconfig.json
main · stable1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
/**
* Grovant senior engineering · 2026 stack
* One repo · one deploy · your IP from the first commit
*/
* Grovant senior engineering · 2026 stack
* One repo · one deploy · your IP from the first commit
*/
export const grovant = {
// WHAT YOUR USERS SEE
framework: "next@16", // fast first load, so visitors stay
react: "19", // smooth under taps
rendering: "ppr+server-actions", // pages render before the user waits
styling: "tailwind@v4", // one design system, no drift
// WHO EDITS THE CONTENT
payload: "3.84", // your team edits without a developer
preview: true, // see changes before they go live
i18n: ["en", "es", "..."], // add languages when you grow
roles: "rbac+access-fn", // no CMS license bill, you control access
// WHERE IT RUNS, WHO OWNS IT
host: "railway", // a preview link for every change
database: "neon-postgres", // standard Postgres you can export
self-host: true, // run it anywhere, no lock-in
media: "r2 | s3", // your files, your storage, your bill
// WHY IT STAYS FAST AND SAFE
qa: "2-pass", // two QA passes before ship
ts: "strict+e2e", // fewer bugs reach you
ci: "lh+budget+ts", // speed checked on every change
a11y: "wcag-2.2-aa", // usable for every customer
} satisfies EngagementManifest;
// repo lives in your GitHub org · same senior every sprint
ts strict·utf-8·LF·spaces · 2
ln 38 · col 1Build kinds · what this stack producesK-01 to K-06
- K-01
Marketing site
request a quote
3 to 6 wks
- K-02
Replatform off WordPress
request a quote
4 to 8 wks
- K-03
Headless CMS build
request a quote
3 to 5 wks
- K-04
SaaS dashboard
request a quote
6 to 10 wks
- K-05
Performance retainer
month to month
rolling
- K-06
Migration project
request a quote
4 to 8 wks
Hire dev on its own. Add design or marketing later from the same senior team, never a forced bundle. The repo is yours from the first commit.
Send the briefWhen the call usually comes in
Why owners hand us the repo.
- Reason 02
Your in-house dev is buried.
Hand us the front-of-house build. It moves in parallel, clean enough for your team to take over.
- Reason 03
You are done babysitting WordPress.
Custom web development on a modern stack, with the repo in your org. Speed checked on every change.
The honest comparison
When one senior is the right answer. And when it is not.
CriterionWordPress + pluginsFreelancerBrand-name studioGrovant
- One named senior engineer on your buildnoyesdependsyes
- Repo in your GitHub org from day onen/adependsdependsyes
- Two QA passes before anything shipsnoraredependsyes
- Type safety end to endnodependsdependsyes
- Speed checked on every changenonodependsyes
- Mutual NDA before repo accessn/araredependsyes
- Senior reply within 1 business daynodependsrareyes
- Free audit before you commitrarerarenoyes
What you get in writing
Clauses I to IV
Four promises.
Signed before code ships.
Who owns the code, who does the work, what happens if you leave. Most builds never write it down. Yours is, before anything is signed.
- §I
You own the repo, always
The repo lives in your GitHub org, not ours. We are a contributor, never the owner. If you leave, you keep everything. The stack is open-source, so any senior can pick it up.
Clause I - §II
Your ideas stay yours
A mutual NDA is signed before we touch your code. Across 8 practices, 0 NDA incidents to date. Every line we write stays yours.
Clause II - §III
Two QA passes before ship
Nothing ships on a single set of eyes. Speed is checked on every change, not once at launch. We fix regressions before the next ticket.
Clause III - §IV
The same senior, every sprint
One engineer is named on day one and signs every deliverable. No SDR layer, no rotating managers, no junior covering.
Clause IV
Signature
You can leave after the first sprint. We would rather you stay because the build is good.
Release train · git log · sample sprint · sample format
Your month reads like git log.
One sprint cycle, start to ship
~/your-repo · git log --graph --oneline
$ git log --graph --oneline --decorate
- (sample)(HEAD, main)release:monthly review ships to your inboxAccount owner·sprint close·prod
- (sample)(tag: release)release:production deploy, two QA passes cleanSenior eng·release·prod
- (sample)(origin/sprint-02)chore(ci):speed + Lighthouse checks enabled on every changeSenior eng·mid-sprint
- (sample)(origin/main)feat:sprint 02 scope locked, signed in your owner docAccount owner·mid-sprint
- (sample)(origin/sprint-01)fix:P0 fixes shipped to preview, slow taps fixedSenior eng·early
- (sample)(origin/audit)feat:issues logged, baseline captured, sprint 01 scopedSenior eng·onboarding
- (sample)(origin/audit)chore:build audit shipped, Lighthouse baseline capturedAccount owner·onboarding
- (sample)(init)init:repo access shared, mutual NDA signed, onboarding openAccount owner·day 01
→ your free audit lands in 4 business days, then a senior runs the same checks every sprint
two QA passes every ship·same senior every sprint
head · mainNo status decks. The repo is the report. Your audit lands in 4 business days.
Start the auditEngineering questions
What you ask before you hand over the repo.
Plain answers on ownership, QA, privacy, self-hosting, and how it runs.
You approve a written scope and price before a line is written, so you are never surprised by the bill. A senior with about a decade in development does the work, and every project clears two QA passes. Month to month support after, so you keep it only while it earns its place.
Most likely. We work in React, Next.js, Vue, Angular, Node.js, Python, PHP, WordPress, Shopify, Flutter, React Native, Swift, Kotlin, Laravel, and more, and we match the stack to what your project actually needs, not what we feel like using.
Yes. We regularly pick up live projects, whether that is adding features to a custom app, rebuilding a WordPress site, or fixing an e-commerce store. We do a code review first and give you an honest read before we commit your money to it.
You get month-to-month maintenance: bug fixes, security updates, performance monitoring, and small feature additions. No lock-in, so you keep it only as long as it is useful. A real senior replies within 1 business day when you need them.
Every project clears two QA passes: automated testing, manual browser and device checks, accessibility, performance, and a security review. You get production-quality code, signed off by one named owner before it ships, not a rushed handoff.
All of it. You get the complete source code, documentation, deployment guides, and admin logins, all in your accounts. We run a walkthrough with your team and stay on through a support period. The work and the access are yours, with nothing held hostage.
Don't see your question?Send a quick message →
Reply · within 1 business dayStill have a question? Ask it in the brief. A senior reads every one within 1 business day.
What happens after you send
Three steps. Four business days.
You send your site. The audit lands 4 business days later. No call needed.
- 01Within 24 hours
A senior replies
A real senior, not an SDR. They confirm scope and send the NDA. The same person who runs your build.
- 02Days 2 to 3
We run your build audit
We audit the code: speed, page weight, type safety, ship checks, accessibility, search markup. No call required.
- 03Day 04
Your plan and price land
The scorecard, a sprint plan, your engineer's name, and a price. Retainer or project, month to month either way.
No drip campaign. A real plan from a real senior, free, in 4 business days.
Start step 01File · DEV-2026/Closing brief
Page 09 of 09
One step
Send the site.
We will send back a scorecard.
A Lighthouse run, a full audit, a plan, and a price in 4 business days. Month to month, cancel anytime.
- 01Free audit in 4 business days
- 02One senior named on day one
- 03Repo in your GitHub org
- 04Two QA passes before ship
Rather talk first?
Book a 20-minute call with a senior~/dev-2026/audit
$ grovant audit --site=your.site
Free Lighthouse audit
Form 02 / 02Send the site. Scorecard comes back in four.
Five fields. A senior replies within 1 business day.
File sealed · Read by a senior engineer
Free Lighthouse · 4 biz days
Senior engineering, repo stays yours