
How to get your company cited by ChatGPT
Most advice on this starts with how to write. That is the third thing that matters. The first two are whether a crawler can reach you, and whether anyone else mentions you.
What we've learned building software with remote teams — speed, quality and everything between.

Most advice on this starts with how to write. That is the third thing that matters. The first two are whether a crawler can reach you, and whether anyone else mentions you.

Most of GEO is SEO you should already be doing. The genuinely new parts are few, specific, and worth separating from the noise.

Every list like this is published by a company that appears on it, including this one. Here is how to read them anyway, and what to ask.

One person writes the spec and approves the release. Between those two moments, a chain of agents plans, builds, reviews, tests and ships. Here is the wiring.

Shipping is the easy half. The expensive half is the three years afterwards, when something breaks at 4am and a human has to be awake for it.

The honest answer is smaller than it was and larger than the marketing says. Here is which work actually moved, phase by phase.

The rewrite is the most expensive possible response to a problem you have not measured. Here is the order to look in, and what each answer means.

The instinct is to rewrite it. The first two weeks should be spent making it legible instead — and the database will tell you more than the code does.

There is no prompt that fixes this. What there is: a set of design decisions that decide how much damage a successful injection can actually do.

Everyone asks what the build costs. The number that decides whether the business works is the one that arrives every month afterwards, forever.

Start with the database you already run. The interesting question is not which is better, but what specifically would make you move.

Most MVP quotes are wrong for the same reason: they price a feature list instead of a decision. Here are the real ranges and what actually moves them.

The hard part is not the model. It is choosing which job to give it, and building the parts around it that decide whether anyone trusts the output.

A demo costs a weekend. A version you can put in front of customers costs considerably more, and almost none of the difference is the model.

Everyone claims senior engineers and agile delivery. Here is how to tell the difference, using things you can check rather than things you are told.

A one-file proposal for telling language models what your site is about. Cheap to add, genuinely useful — and widely misunderstood.

We allowed every AI crawler in robots.txt. Cloudflare was still returning 403 to all of them. Here is how to find out if that is happening to you.

Most teams asking this question do not have a queue problem yet — they have work happening inside the request. That changes which answer is right.

Ordering the wrong one is the most expensive mistake in early product work. Each answers a different question — and only one of them is meant to have users.

Teams reach for fine-tuning when they want the model to know something. That is the one job fine-tuning is worst at.

The rewrite is the failure mode, not the plan. Here is how to extract services one seam at a time while the thing stays live.

Success is the failure mode. The shortcuts that got you to launch are exactly the ones that break when launch works.

Ranking first is worth less when the answer appears above the results. Being the source that answer cites is the new position one.