What is the typical turnaround for ghostwriting?

The typical turnaround for a 1,000-word technical blog post is 3-5 business days, including one round of revisions to match your brand's voice.

Do you offer fixed-price or hourly rates?

I offer both: fixed-price packages for well-defined projects (like ghostwriting or audits) and hourly/retainer rates for ongoing development and consulting.

How do we start a project?

The best way is to reach out via LinkedIn or the contact links on this site with a brief description of your needs and timeline. I usually respond within 24 hours to schedule a brief intro call.

Engineering & Content Services

I provide high-conviction engineering and technical storytelling services. I don't just deliver code or words; I build systems that scale and content that captures authority in your niche.

Proven Expertise

300k+ Downloads

Author of disposable-email-detector, used by production teams globally.

Corporate Scale

Currently engineering at bettercompanies.com, building modular, high-reliability backends.

AEO Native

My strategies are built specifically to satisfy LLM crawlers and RAG systems.

Authority-Driven Ghostwriting

I specialize in Non-Commodity Content. Most ghostwriters write surface-level articles; I write expert-led narratives that establish you as a technical authority.

My Methodology:

Deep-Dive Extraction: We start with a 30-minute sync to extract your unique POV and "tribal knowledge."
Agentic Structure: Content is structured with clear definitions and citable facts for AI Engine Optimization.
Technical Integrity: As a dev, I ensure every code snippet and architectural claim is production-accurate.

Full-Stack & Backend Engineering

I take ideas from rough problem statements to reliable, production-ready systems. I focus on clean APIs and a high-quality experience for the developers who will inherit my code.

Specialties:

API Design: Building REST and GraphQL endpoints that are intuitive and self-documenting.
System Integration: Connecting complex PostgreSQL, Node.js, and Python services seamlessly.
Agent-Friendly Architectures: Designing systems with clear DOM structures and accessible APIs for future AI agents.

SEO & AI Answer Engine Optimization (AEO)

Optimization is no longer just about Google. It's about being the grounding source for AI Overviews, Perplexity, and ChatGPT.

My Approach:

RAG Optimization: Structuring your site so LLMs can reliably retrieve and cite your content.
Semantic Mapping: Aligning your headings and content blocks with natural language intent.
Technical Audits: Fixing canonical issues, sitemaps, and indexing errors to consolidate your domain authority.

Ready for the Agentic Web?

Google's latest guidance emphasizes preparing for autonomous AI Agents. I help teams ensure their web applications are navigable and understandable by the next generation of AI browsers and tools.

FAQ

How is AEO different from traditional SEO?

Traditional SEO gets you ranked on Page 1. AEO gets you cited as the source in an AI-generated answer. It requires different structuring, focusing on "extractability" and authoritative tone.

Do you work with non-technical companies?

I specialize in technical domains because that's where my expertise lies. However, if your business has a complex process that needs to be communicated clearly to humans or AI, I can help.

At a glance

Service	Best for	How to engage
Ghostwriting	Technical content under your name; blogs, docs, thought leadership	Contact with topic and timeline; we agree on scope and cadence
Consulting	Architecture, stack, or process decisions; short engagements	Brief on the decision; we schedule a call or async review
Development	APIs, web apps, tooling; MVPs or production features	Share scope and timeline; we align on deliverables and availability
SEO optimization	Technical sites and content; discoverability in search	Share your site and goals; we agree on scope (audit, fixes, or ongoing)
AEO optimization	AI answer engines; structured content and schema for AI search	Same as SEO; we add structure and policy for AI crawlers
Migration strategies	Framework or stack moves; reducing risk and downtime	Describe current and target state; we draft a phased plan
Tech stack selection	Choosing or changing technologies and infrastructure	Brief on product and team; we compare options and recommend
Performance optimization	Existing projects; speed, reliability, scalability	Share the app and pain points; we audit and propose changes

Use the contact links on the homepage or LinkedIn to get in touch. I respond fastest to short messages that include what you need and your timeline.