Kansaifixer

Built internal process automation for Kansaifixer, a content and lifestyle platform for immersive Japan travel, cultural education and local living experiences.

The problem

A content operation looks like writing from the outside. From the inside it is mostly the work around the writing: preparing material, moving it through to publication, keeping what already exists accurate, and repeating all of that on every piece.

That surrounding work scales linearly with output while the writing does not, so past a certain volume the routine becomes the thing limiting how much gets published. For a publication whose value accumulates in its archive rather than in its newest post, that ceiling is expensive — it caps the asset.

Constraints

Content is the product, so anything introduced between having something to say and it being live gets paid for in output. Automation had to remove steps rather than add a system to be managed.

The people it serves are editorial, not technical. Tooling that requires an engineer to operate does not survive contact with a publishing schedule, so it had to run without supervision and be obvious when it did not.

What I built

Automation for the internal processes behind the publication, in Python — the repetitive operational work that happened the same way every time and only needed a person because nothing else was doing it.

Outcome

Less of the operation’s time spent on routine and more of it available for the material itself, which for a publication is the only input that matters.