From our blog
Articles & blogs
- Ebook Publishing
- Delivery & Ops
- Security & Compliance
Guides
Practical Guides
Step-by-step resources to help you evaluate use cases, plan implementation, and roll out automation with confidence.
FAQ
Common questions
Everything you need to know before we start working together.
Do I retain ownership and copyright of my book?
Your manuscript remains your work. We document publishing-account ownership, rights information, files, and the responsibilities in the project agreement. Copyright registration and legal requirements depend on your jurisdiction.
Do you offer ongoing support after launch?
Yes. Post-launch help can be included in the agreed scope, and ongoing support can be arranged for future updates, changes, or publishing needs.
What’s the difference between ebook and audiobook publishing?
Ebook publishing prepares and distributes a written digital book. Audiobook publishing additionally involves narration, audio editing, quality checks, and audio-platform delivery. We can scope either format or both.
Do you build with page builders or custom code?
We use WordPress and Elementor where editable layouts make sense, and custom PHP or Laravel when requirements call for additional business logic or integrations.
What access do you need to my website or accounts?
Only the access needed for the agreed work. That may include WordPress or hosting, relevant CRM or API tools, or your publishing accounts. We explain required permissions before requesting access.
Can you work with our existing tools and vendors?
Yes. We review your existing website, tools, and workflow first, then identify which systems can be reused and which connections need additional work.
Do you offer ongoing maintenance?
Yes. Maintenance can be scoped to include updates, backups, monitoring, fixes, and requested changes. We agree on the frequency and responsibilities before support begins.
What if we're not sure what to automate first?
We start by mapping where repeated manual steps, errors, or slow handoffs occur. Then we select a small, measurable first workflow and expand only when it proves reliable.