What you'll see, and what you'll own
Hiring a team to build software usually means trusting a process you can't see. These pages show every step of how we work, and list what moves into your name at the end, so you know both before you send a word.
Zaions is a software agency. We build web and Android apps, browser extensions and desktop apps, and we do the design, video, QA and AI work around them. We also built and still run 15+ products of our own.
Four steps, every project. You send the brief. You get a written plan and estimate before we write a line of code. Every milestone ends with a link to the working build, so you click through progress instead of reading a status report, and at handover the code, the design files, the accounts and every credential move into your name.
Who are these docs for?
You, if you're thinking about hiring us, or you already have.
They're written for founders and small-business owners who know what the business needs and don't want to babysit developers to get it. We assume no technical background. Where a technical word is unavoidable, it comes with its meaning in the same sentence, like a code repository, where all your source code lives.
How do these docs relate to zaions.com?
zaions.com is the short version. These pages are the long one.
The agency site tells you what we do and shows the products we run. The docs explain how each part of a project works: what a good brief contains, what a milestone link opens, what moves into your name at handover, and how to pay an invoice once you're a client.
These pages quote a few figures, like the package prices and the phone number. zaions.com is the authority for them, and where the two differ, zaions.com wins:
- the current package prices, on Pricing (opens in a new tab)
- the payment methods, which only zaions.com lists, on Payments (opens in a new tab)
- the phone number and email addresses, on Contact (opens in a new tab)
If a figure here differs from your written estimate, the figures in your estimate are the ones for your project. These pages are written for everyone.
What's in here?
Read them in order if you're starting out and haven't sent a brief yet, or jump straight to the one you need if you're already a client with a project running.
- Writing your brief: what to put in it, with an example, and what happens after you send it.
- How a project runs: from the brief to the written plan, through every milestone link, to the handover.
- Packages explained: the free consultation, Launch, Build and Team, plus add-ons and the work that gets its own estimate.
- What you own at handover: the checklist, by kind of project.
- Paying an invoice: where the methods are and which reference to add.
- Open-source tools: windowsweep, macleanup and linux-cleanup, with their public repositories.
- Questions: short answers to what people ask before they hire us.
Next: Writing your brief: what to put in it, and what happens after you send it.