Corey Corey
How it worksWhat Corey buildsCase studiesYour dataDocsStart with Corey
Running

kristianpapadakis.com - the founder's own site

The personal site and writing of the person who builds Corey - separate from the company, on purpose.

A personal site kept deliberately separate from Presso Network and from Corey. It exists because the person and the company need different voices, and because a founder writing under their own name is the cheapest distribution a one-person business has. Corey runs the publishing routine so it does not decay.

The facts

What this is, on the record

Started
27/02/2026
Commits
63
Status
Running
Who did what
Built by Kristian Papadakis. Predates Corey; Corey now handles the publishing routine.
Built with
Astro, Tailwind, Cloudflare

The project

Three public sites, three audiences. Presso Network sells to event organisers. getcorey.ai sells Corey. And there is a personal site, under the founder’s own name, which sells nothing.

Keeping them separate takes more effort than folding the personal writing into a company blog. It is still the right call, because the voices are not interchangeable. A company blog cannot really hold an opinion - everything it publishes becomes policy. A personal site can be wrong in public, change its mind, and write about something that has nothing to do with the product.

For a one-person business that also happens to be the cheapest distribution available. People follow people.

What we did

Started from an existing Astro theme rather than designing from scratch, and put the saved time into the businesses that generate revenue.

That is a small decision that says something about the rest. Everything in this portfolio is built by one person, which means the real skill is not building things well. It is knowing which things deserve to be built well and which just need to exist. A personal site is a distribution channel. Nobody subscribes because of the typography.

The stack matches everything else - Astro on Cloudflare - so there is one set of conventions across all the public sites rather than four separate ways of doing the same job.

What Corey does with it

Publishing on a rhythm.

This is the least urgent work in the portfolio and the first thing to disappear under pressure. Nothing breaks when personal writing stops. No customer chases it, no invoice goes unpaid, no deadline is missed. It just quietly stops, and six months later there are three posts from last year.

Which is precisely why it is worth handing to an operator. The work that has no deadline is the work that only ever happens if something other than your memory is responsible for it.

The calls

What we decided

Keep the person separate from the company

Presso Network has a site, Corey has a site, and the founder has a site. Merging them is tempting because it is less to maintain, and wrong because they speak to different people. The company voice sells a service; the personal one is where an opinion can be held without it becoming corporate policy.

Start from an existing theme

Built on an off-the-shelf Astro theme rather than designed from nothing. A personal site is a distribution channel, not a design exercise, and the hours saved went into the businesses that make money. Not everything needs to be bespoke, and knowing which things do is most of the skill.

Same stack as everything else

Astro on Cloudflare, matching the other public sites. One stack across the portfolio means one set of conventions, one deployment story and one place to learn a lesson, rather than four half-remembered setups.

The output

What got built

  • A personal site and blog at 63 commits, on Astro and Cloudflare.
  • Posts, projects and notes as separate content collections.
  • Comments and syntax highlighting, kept lightweight.
Going forward

What Corey runs now

The publishing routine

Drafting, editing and getting posts out on a rhythm rather than in bursts, which is the difference between a personal site that compounds and one with three posts from last year.

Keeping it consistent with the rest

Same stack and conventions as the other sites, so a fix learned in one place is applied everywhere rather than rediscovered.

What this became

This is the smallest project in the portfolio and it makes the clearest point. Personal writing is the first thing to slip when a business gets busy, because nothing breaks when it does - no customer complains, no invoice goes unpaid, it just quietly stops. That is exactly the class of work an operating system is for: valuable, recurring, and entirely dependent on someone remembering. Corey runs it precisely because it is the kind of thing a human stops running.

Run yours the same way

Everything above is one operator across a portfolio. Corey is that operator, packaged. 28 days on us, no card.

Start with Corey →