Skip to content

What changed in the docs

When we change how a project runs, the page that explains it changes the same week. Newest first.

  1. Other ways to get it built, compared

    How a Zaions project compares with a big agency, a solo freelancer, building it yourself with AI, hiring your own team or renting developers by the hour.

    Read the page

  2. Coming from an AI app builder

    How a Zaions project runs next to building your app yourself with an AI or no-code tool, and how to bring what you built to us as a brief.

    Read the page

  3. Coming from a big agency

    How a Zaions project runs next to a big agency: who answers your brief, how you see progress, what you own at the end, and when the big agency is the better choice.

    Read the page

  4. Coming from hourly developers

    How a Zaions project runs next to renting developers by the hour: who plans the work, what sets the price, and when hourly developers are the better choice.

    Read the page

  5. Hiring your own team instead

    How a Zaions project compares with hiring your own developers, and how a first version built by us hands over to the team you hire later.

    Read the page

  6. Coming from a solo freelancer

    How a Zaions project runs next to hiring one freelancer: which jobs one person covers well, and what a team adds for design, testing and the handover.

    Read the page

  7. Page tours and How working with Zaions works

    Take a tour of any main page on zaions.com, or read How working with Zaions works: six steps, from picking a service to handover.

    Read the page

  8. What you'll see, and what you'll own

    How a Zaions project runs, step by step: writing the brief, the written estimate, milestone links, the packages, the handover and paying an invoice.

    Read the page

  9. Writing your brief: what to include

    What to put in a Zaions brief, field by field, with an example of a good one. Only your name and email are required; a napkin sketch is a fine start.

    Read the page

  10. Questions before you hire us, answered

    Short answers about Zaions: who owns the code, what an app costs, how progress is shown, scope changes, maintenance, running costs and where the team is.

    Read the page

  11. What you own at handover: the checklist

    The code repository and design files move to you at handover, every account ends in your name, and your store listing ships from your own developer account.

    Read the page

  12. How a project runs, from brief to handover

    Every Zaions project runs in four steps: the brief, a written plan and estimate, a link to the working build at every milestone, then a full handover.

    Read the page

  13. Open-source cleanup tools for developers

    Three MIT-licensed disk cleanup tools for developers from the Zaions team: windowsweep for Windows, macleanup for macOS and linux-cleanup for Linux.

    Read the page

  14. Packages explained: which one fits you

    Which Zaions package fits your project, what every package includes, what gets its own estimate, and the running costs your estimate lists beside the price.

    Read the page

  15. Paying an invoice: the reference to add

    How to pay a Zaions invoice or estimate: pick a method on zaions.com/payments, copy the details, and add the reference from your invoice to the payment note.

    Read the page