Editorial and publishing systems
Strategy, governance, workflows, style, ethics, contributor agreements, bilingual operations. Proof: Aware Pakistan, Tribal Post, TNN.
Services
An engagement model, not a price list.
Media organizations, NGOs, and civil society. Founders who want systems they own. Journalists and at-risk teams who need practical protection, not theatre.
Where he is useful
Websites the organization can run
Design, build, launch, documentation, handoff. Static-first, mobile-first. Proof: The Dotani Digital.
More on websites →Digital safety training
Practical sessions for journalists, activists, at-risk teams. Unpaid in the practice. Proof: Bytes For All Training of Trainers, 2014. Twelve years. Not a productized package.
How collaboration runs
- Understand the problem. Paid discovery. A fixed-scope proposal.
- Build against that scope. Documented decisions. Changes in writing.
- Hand off. Documentation, training, deploy, a short support window.
- Leave. No retainer required. The organization runs the system.
What you bring
A real problem, a person who will own the system after handoff, access to the current stack and content, and a decision-maker who can answer in days not months.
What done means
The team can publish, deploy, or train without him in the room.
Not for
- A website with no problem behind it.
- Heavy custom applications as the main craft.
- Growth hacking and vanity metrics.
- Values-misaligned causes.
- Political campaign management.
- AI automation as the identity of the work.