// Graylight — single-page site, Bento direction, solo founder framing. const Arrow = ({ size = 14 }) => ( ); const Logo = () => ( Graylight ); const NavBar = () => ( ); // ────────────────── HERO ────────────────── const Hero = () => (

Software, AI,
and the growth
that pays for both.

A studio of one — by design

Graylight is one senior engineer — twenty years of shipping software for the DOD, public companies, and founders who'd rather not assemble a thirty-person org to build the thing in their head.

Tell me about your project See what I do
{/* Bento */}
{/* Big intro tile */}
What I do
I'm the engineer you call when the "how" is the hard part.
Custom builds, AI integration, and the marketing that makes them compound — handled by the same person, end to end.
{/* Code preview */}
spatial/tile_pipeline.ts 
{`// 18M points → 60fps map.
// Quadtree + worker pool + WASM
// decode. No magic, just patience.

`}export async function{` `}tilePipeline{`(src) {
  `}// stream > load. always.{`
  `}const{` chunks = src`}
            .lazyDecode()
{`
}`}
{/* AI tile */}
03 / AI
AI that earns its line item.
Used well, AI cuts months off a build. Used badly, it's a slogan. I treat it like a tool, not a brand.
{["LLMs", "Agents", "RAG", "Eval"].map((t) => ( {t} ))}
{/* Experience tile */}
20yrs
of shipping desktop, mobile, and web software — including GIS and data-heavy systems for the DOD and public companies.
{/* Process tile */}
How it goes
One call. One plan. Working software in week one.
{/* Marketing tile */}
05 / Growth
Social & content that compounds.
); // ────────────────── SERVICES ────────────────── const SERVICES = [ { n: "01", title: "Custom software", blurb: "Desktop, mobile, web, backend. You bring the idea — I architect, build, and ship it. Twenty years of doing this means I know which corners cut and which ones don't.", icon: }, { n: "02", title: "Hard problems", blurb: "GIS pipelines, data-heavy systems, scaling walls, legacy migrations. The work most agencies politely turn down — that's where I tend to do my best.", icon: <> }, { n: "03", title: "AI integration", blurb: "Real wins from LLMs, agents, and ML — built where they actually move a number for your business. Not a sticker on the homepage.", icon: <> }, { n: "04", title: "Cost & efficiency", blurb: "An engineer's audit of your stack and process. The line items quietly draining your budget — and leaner replacements that don't hurt to use.", icon: }, { n: "05", title: "Social marketing", blurb: "Strategy, content, and analytics across the channels your customers actually live on. Engineering rigor applied to a part of the business that usually doesn't get it.", icon: }, { n: "06", title: "Growth, end-to-end", blurb: "Positioning, funnels, retention loops. Treated like engineering — measured, iterated, compounding — not a one-off campaign.", icon: }, ]; const Services = () => (
Services

Six things,
done well.

I don't pretend to do everything. I picked the problems I'm best at — building, fixing, and growing software products — and stayed there.

{SERVICES.map((s) => (
{s.icon}
{s.n}
{s.title}
{s.blurb}
))}
); // ────────────────── ABOUT ────────────────── const About = () => (
{/* Portrait placeholder */}
Founder & sole engineer
Zak Nixon
Cullman, Alabama · works remote
About

A deliberately small studio.

Hi, I'm Zak. Graylight is me — twenty plus years of software development and architecture, packaged into a consultancy small enough to actually answer the phone.

I've built desktop and mobile applications for the Department of Defense and public companies, mostly tackling GIS and data-heavy problems where the wrong architecture decision quietly costs years. These days I bring that experience to founders who need a senior engineer in their corner — not a fifteen-person agency with a project manager standing between them and the work.

Specialties
GIS · spatial pipelines · data-heavy systems · desktop & mobile
Worked with
Department of Defense · public companies · early-stage founders
Currently taking new projects — usually one or two at a time so each gets the attention it deserves.
); // ────────────────── PROCESS ────────────────── const Process = () => (
How a project goes
From "I have an idea"
to "it's live".
typical timeline · 6–14 weeks
{[ { n: "01", t: "Listen", b: "One call, one written brief. I mirror back what I heard so you can correct me before time gets burned." }, { n: "02", t: "Shape", b: "A short, opinionated plan. Real estimates, real tradeoffs, no consultant-speak." }, { n: "03", t: "Build", b: "Weekly demos, direct communication, working software in your environment from week one." }, { n: "04", t: "Hand off", b: "Docs, runbooks, and an engineer who's actually on call until you don't need one." }, ].map((p) => (
{p.n}
{p.t}
{p.b}
))}
); // ────────────────── CONTACT ────────────────── const Contact = () => { const [form, setForm] = React.useState({ name: "", email: "", phone: "", service: "", timeline: "", source: "", msg: "", }); const [submitted, setSubmitted] = React.useState(false); const [touched, setTouched] = React.useState({}); const set = (k) => (e) => setForm({ ...form, [k]: e.target.value }); const touch = (k) => () => setTouched({ ...touched, [k]: true }); const emailValid = /^[^@]+@[^@]+\.[^@]+$/.test(form.email); const valid = form.name && emailValid && form.service; const submit = (e) => { e.preventDefault(); if (!valid) { setTouched({ name: true, email: true, service: true }); return; } setSubmitted(true); }; return (
{/* Form column */}
Let's figure it out together

Tell me what you're
trying to build.

Even half-formed ideas are fine — that's often where the best work starts. I'll reply within one business day with thoughts and next steps, never a sales script.

{submitted ? (
Got it, {form.name.split(" ")[0]}.
I'll be in touch at {form.email} within one business day. In the meantime, feel free to reply with anything else that comes to mind.
) : (
I reply within one business day. Your details stay between us.
)}
{/* Contact info column */}
); }; // ────────────────── FOOTER ────────────────── const Footer = () => ( ); // ────────────────── APP ────────────────── const App = () => ( <>