Non-profit · Workflow automation + AI · [X] weeks · [price range]

    Every project kickoff cost two hours of admin. Now it's one file upload.

    NGO Crventivizam launches projects constantly. Each one meant a coordinator setting up tasks by hand and a copywriter drafting from scratch. I built a workflow that reads the project documentation and does both — ready for a human check in five minutes.

    ~2 hrs
    saved per project, every time
    5 min
    from upload to tasks and drafts
    [X]
    projects a year · [X × 2 = Y] hours back
    NGO Crventivizam screenshot

    This is your situation if…

    • Every new project, campaign or client starts with the same setup: read the brief, create the tasks, brief each person — by hand.
    • Your team writes first drafts of posts, articles or announcements from a blank page, even though the source material already exists.
    • You're a small team with no budget for software that sits unused — it has to fit how you already work in Asana, Google Drive or Telegram.

    The problem

    Each time a project launched, the coordinator spent about 45 minutes reading the documentation, pulling out the key points and creating Asana tasks for every team member. At the same time, the copywriter spent one to two hours preparing social media copy, blog posts and publication drafts from scratch.

    The work followed the same pattern every time. It was repetitive, it was slow, and it ate the hours the team was actually hired for — the creative and strategic part. People dreaded kickoffs.

    What I built

    In the order it happened.

    1. 1
      Mapped the kickoff, step by step.

      From document upload to the last task assigned — and asked what the team would realistically use, not what would look impressive.

    2. 2
      One trigger: upload the documentation.

      The file lands in a shared folder and the workflow starts. Nobody has to remember to run anything.

    3. 3
      AI reads it and decides what's needed.

      How many social posts, which blog articles, which publications, what the technical team has to update on the website.

    4. 4
      First drafts, written in the same run.

      Social copy with notes for the designer, full blog post drafts, publication drafts — all into shared Google Docs for the copywriter to review before anything goes out.

    5. 5
      Asana tasks created and pre-filled.

      The main project task and a subtask for the coordinator, copywriter, designer and technical lead — each with the right materials attached.

    NGO Crventivizam - additional screenshot

    Tasks and drafts waiting in Asana before the kickoff meeting ends.

    For technical readers: how it's built

    n8n workflow triggered by a Google Drive upload; document analysis and content generation with ChatGPT; Asana API for task creation; Google Docs and Sheets for review; Telegram notifications to the team. Built with Claude Code. [confirm details]

    Claude Code
    n8n
    Asana
    ChatGPT
    Google Drive
    Telegram

    What changed

    Measured [X months] after launch.

    ~2 hrs
    saved on every project kickoff
    45 → 0 min
    of manual task setup for the coordinator
    5 min
    from upload to a kickoff that's already set up
    [X]
    projects run through it so far
    Duration:
    [X weeks]
    Investment:
    [price range]
    Team on my side:
    just me
    Runs in:
    the NGO's own accounts [confirm]
    “We're an NGO — we don't have budget for software that sits unused. Stefan asked what our team would realistically use, not what looked impressive on a demo. We saved ~2 hours per project on coordination work nobody enjoyed anyway.”
    Željka JojićŽeljka Jojić
    President, NGO Crventivizam

    Small team, repetitive setup work? Let's talk.

    30 minutes, free, no commitment. You talk to me from the first call to delivery. Or write to iveticpf@gmail.com.

    Book a free 30-minute call