For when four people publish and it reads like four people. A new hire ships their first usable brief in week one instead of month three, a rule changes in one file rather than in five heads, and you can point at why a decision was made six months ago.
Mobility and fleet operations, SME finance and lending, hospitality, industrial and manufacturing. Built for multi-team operations where more than one person publishes.
For when a competitor gets named in an AI answer and you do not, or traffic sits flat while the page count keeps climbing. You get the schema that makes your pages readable to an answer engine, and a report that says which fix to make first.
Sports and media, software and technology services, mobility and fleet operations. Suited to sites that need to be cited by AI assistants, not only ranked.
For when the newsletter stopped in month three, or nobody can say whether a given email is a receipt, an announcement, or marketing. Templates your team fills in without asking first, and a cadence that survives the person who set it up leaving.
Real estate and property platforms, SME finance publications, subscription and membership media. Built for teams sending both transactional and editorial email.
For a launch, a rebrand, or a site where every page sounds like whoever happened to write it. One voice across the lot, built section by section, homepage last because it has to reference what the other pages actually ended up saying.
Automotive, retail and F&B groups, risk and compliance services, hospitality, and multi-entity conglomerates holding one voice across separate business lines.
For when you run a public space you are answerable for and a moderator has to make a call at 11pm with nothing to point to. Guidelines that settle the hard cases in advance, a right of reply, and a record of what was decided.
Trust and safety platforms, security and risk services, and consumer brands running a public community they are accountable for.
Real material first, drafting second.
The hard part is never the writing, it is getting substance out of the people who have it, so sourcing is its own workflow with its own gate. Then three shapes for written pieces, a separate set of rules for anything read aloud, and a confidentiality filter that runs before drafting rather than before publishing.
Write the states nobody remembers.
An inventory of every string that already exists, which usually finds three words for the same action and a placeholder that reached production. Then the screens, and the states that ship as whatever the developer typed: empty, loading, partial, error, success.
All prices shown in USD. If you need to pay in MMK, the exchange rate will be confirmed at the time of invoicing based on that day’s market rate. Myanmar’s official and market rates can differ significantly, so a rate quoted in advance would not reflect what you’d actually pay.
Mix tiers across disciplines freely — Website & Landing Copy at Enterprise next to Search & Answer Visibility at Start-Up is a normal thing to buy. What a mix loses is the matching-tier discount, which is why the pairs above say “matching tier”. The Full Workflow is the one exception: always a single tier across all five packages, never mixed.
Every proof point above traces to real delivered work. No client names appear on this page by design; ask if you’d like specific references for your industry.
A package is work I do for you: you get the articles, the pages, the audit, the emails, finished. A system is the way that work gets made, handed to your own team — the workflows, the gates, the templates, the failure modes, and one configuration file you fill in with your own tools and approvers. Buy a package and you own that deliverable. Buy the system and your next hire produces one in their first week. Most people start with a package, and the ones who buy a system have usually seen the package first.
The Four-Beat Checker, on GitHub, with no signup and no email capture. It reads a guide or how-to draft and tells you which of the four beats is missing and which single fix would do the most. It is the whole package rather than a teaser, and opening the repository is the clearest way to see what a system actually looks like before you pay for one. The product guide has the links.
The licence goes to the company on the invoice and its wholly-owned subsidiaries, not to a person or a seat, so any number of your staff and contractors can use it for your own work. It is perpetual for the version you bought — nothing renews, nothing switches off. You can modify your copy internally; you cannot resell it, publish it, or build a competing product out of it. There is no obligation on me to ship updates, so a system you bought two years ago reflects two-year-old practice: that is the trade you make for a licence that never expires.
Tick what fits, send it, and nothing happens to your money. Within 3-5 business days you get back either questions or an order form with scope, price and dates on it. You sign that, the deposit clears, work starts. Nothing on this website is a contract — the order form is the first thing that is.
Invoices go out once scope is agreed. A 60% deposit is due to begin the engagement, with the remaining balance due on delivery. Work does not start before the deposit clears, and final files are handed over once the balance is settled.
Mobile wallets (KBZPay, WavePay) and bank transfer (KBZ Special Account, Yoma Flexi Everyday Account) for Myanmar-based payments. International transfer and other arrangements are available on request. Prices are quoted in USD; payment in MMK is possible at a rate confirmed on the invoice date.
Because most of this work is for clients across Southeast Asia, and one stable currency is easier to compare than six. Myanmar's official and market rates can differ significantly, so no MMK rate is quoted in advance — it is confirmed on the invoice date and applies to that invoice only.
Both, and most people start with a project. You buy the build once, see whether we work well together, and only then decide about anything monthly. Where a package includes an ongoing cadence — a monthly newsletter, a recurring pulse report, a post schedule — that carries on as a retainer, quoted per month once the build is delivered.
Say you send notes on Monday, your colleague adds two more on Tuesday, and on Wednesday you remember a third thing. That is one round, not three, because I had not restarted work yet. The count moves when I begin acting on it, not when you hit send, so you can add to it or pull something back at no cost until then. Asking for a new page or a new channel partway through is not a revision — that is new scope, and it gets a price before it starts.
A Start-Up job is usually a week or two. Scale-Up runs three to five weeks. An Enterprise build is six to ten weeks, depending on how much already exists to work from. Every one of those assumes your feedback lands inside the window on the order form — a week of silence moves delivery by at least a week, which is arithmetic rather than a penalty. Real dates go on the order form; these are for planning.
Yes. Scale-Up website copy next to Start-Up email is a normal thing to buy, and three or four done-for-you disciplines at one matching tier earns 15% off. Systems work the same way, with their own 15% for two or more at one tier. The one exception is the Full Workflow bundle: a single tier across all five, never a mix, because what you are paying for there is the five running as one system rather than five suppliers who happen to share an invoice.
You do, once the balance is paid. Use it, change it, sell the business with it — the copy, the pages, the briefs, the reports, the rule files. Ownership moves on payment rather than on delivery, so files sent before the invoice clears are yours to review, not yet yours to publish. What stays mine is the method behind them: the templates and frameworks I build with, which I keep using for other clients.
Yes, as part of the workflow, and openly. Nothing reaches you unread — every deliverable is reviewed, edited and fact-checked by me, and I answer for it as my own work. Your confidential material is not used to train third-party models. The place AI actually earns its keep is not the drafting: it is the rule files and routers that let a new hire produce something on-brand in their first week.
If you need someone to build the site, run the ads, or press publish on your channels, that is not this — I work alongside whoever does. Also outside scope: image sourcing and licensing, translation, and legal or regulatory sign-off on anything you publish.
Say so in writing and it ends — no notice period, no argument. You pay for work done to that date, and the deposit covers it up to its value. What you will not get back is the deposit itself once work has started, because it reserved time that cannot be resold after the fact.