Sojournii uses cookies for product analytics and, once you accept, marketing measurement. You can change this anytime. Learn more
Early access — Sojournii is under active development. Not all features here are live yet. Have a question? Contact us
Engineering
Field notes from the team. Payments, infrastructure, and the technical decisions behind a booking platform that handles real money.
We moved Sojournii's recurring marketing work from bursty manual generation to a slower Jira, Confluence, Paperclip, and GitHub workflow. This is what the architecture does, why each boundary exists, and where the tradeoffs still show.
Dale Baldwin
Founder, Sojournii
Latest posts
We ship most of our day-to-day engineering work through an agent-driven pipeline now. JPD captures ideas, Confluence holds the design + RFC + drift docs, Jira tracks epics and stories, and GitHub does the code. This post is a brief tour of what each tool earns its place doing — and why we still pay Atlassian even with most of the implementation labour automated.
We swapped GitHub-hosted runners for Blacksmith runners on every job in our CI pipeline. The effect on humans was a faster build. The effect on our agent-driven implementation pipeline was structural — what used to be "submit a PR and check back tomorrow" became "merge six PRs in an afternoon, with full review on each".
Monthly, at most
One short email when we publish. No drip sequences, no upsell emails, unsubscribe anywhere.
Flat monthly pricing from A$50. Own your guests. Keep the cashflow.
