Five Portfolio Projects That Prove Automation Skills, No Code Needed

The fastest way to prove you can automate is to show automations you have built. Not certificates, not tool lists on your CV, but working projects with clear documentation. These five no-code portfolio projects cover the skill areas employers and clients ask about most. Each one uses free tools and solves a problem that real Kenyan businesses face.

Why a portfolio matters more than credentials

When a business owner in Nairobi needs someone to automate their customer follow-ups, they are not going to ask for your GPA. They want to see that you have done something similar before. When a hiring manager reviews applications for an operations analyst role, the candidate who shows a working automation stands out from twenty candidates who list "Zapier" under skills.

Your portfolio is your proof of work. It answers the question "can this person actually build something useful?" with evidence instead of claims.

The projects below are designed to be built with free tiers of no-code tools. You do not need paid subscriptions to create them. You do not need coding knowledge. You need a few hours per project and the willingness to learn as you build.

Project 1: Customer inquiry router with auto-response

The problem it solves

A small business receives customer inquiries through a Google Form (or similar intake). Each inquiry needs to go to the right person: sales questions to the sales lead, support issues to the support team, partnership requests to the owner. Currently, someone reads every submission and forwards it manually.

What you build

An automation using Make or Zapier that:

• Triggers when a new Google Form submission arrives
• Reads the inquiry type from a dropdown field in the form
• Routes the submission to the correct person via email
• Sends an automatic confirmation to the customer with a personalized message based on their inquiry type
• Logs every submission in a Google Sheet with timestamps

Tools needed (all free tier)

Google Forms, Google Sheets, Make (free plan) or Zapier (free plan), Gmail.

Skills this demonstrates

Triggers, conditional logic (routing based on field values), multiple actions from a single trigger, data logging, and customer-facing automated communication.

How to document it

Take screenshots of your automation flow. Record a short screen video showing a test submission flowing through the system. Write a one-page case study: the problem, your solution, and how it eliminates manual routing. If you build this for an actual business (even a friend's side hustle), include their brief testimonial.

Project 2: Weekly report generator

The problem it solves

A business owner tracks daily sales or activities in a Google Sheet. Every Friday, they manually pull together a weekly summary: total sales, top products, average order value, notable changes from the previous week. This takes an hour or more and sometimes gets skipped.

What you build

An automation that:

• Runs every Friday at a set time
• Pulls the current week's data from the Google Sheet
• Calculates key metrics (totals, averages, comparisons to the previous week)
• Formats the results into a readable summary
• Sends the report via email to the business owner (and optionally to WhatsApp via a webhook)

Tools needed (all free tier)

Google Sheets (with formulas for calculations), Make or Zapier, Gmail. Optionally, a free ChatGPT API call to generate a natural-language summary paragraph.

Skills this demonstrates

Scheduled automations (time-based triggers), data retrieval and calculation, formatted output, and optional AI integration for text generation.

How to document it

Show the Google Sheet with sample data. Screenshot the automation flow. Include an example of the generated report email. If you added the AI summary feature, show the prompt you used and explain why you included a human review step.

Project 3: Lead capture and follow-up sequence

The problem it solves

A Kenyan service business (consultant, tutor, photographer, event planner) gets leads from their website or social media but follows up inconsistently. Some leads get a response within an hour. Others wait three days. Some fall through the cracks entirely.

What you build

An automation that:

• Captures leads from a Google Form embedded on a website or shared via social media
• Immediately sends a thank-you email with relevant information (pricing, next steps, a scheduling link)
• Adds the lead to a Google Sheet CRM (contact name, date, inquiry type, status)
• Sends a follow-up email three days later if the status has not changed to "responded"
• Notifies the business owner via email when a new lead arrives

Tools needed (all free tier)

Google Forms, Google Sheets, Make or Zapier, Gmail. Optionally, Calendly's free tier for scheduling links.

Skills this demonstrates

Multi-step automations, delayed actions (the three-day follow-up), conditional checks (only follow up if status has not changed), CRM-style data management, and end-to-end lead handling.

How to document it

Map out the entire lead journey visually (a simple flowchart works). Show the automation steps. Demonstrate a test lead flowing through the system from form submission to follow-up email. Write a brief explanation of how this solves the inconsistent follow-up problem.

Project 4: Social media content scheduler with approval

The problem it solves

A small marketing team or solo marketer creates social media posts in batches. They want to draft posts, get them approved by a manager or client, and then schedule them for posting. Currently, this happens through scattered WhatsApp messages and email threads.

What you build

An automation that:

• Reads post drafts from a Google Sheet (columns: platform, post text, image link, scheduled date, status)
• When a draft is marked "ready for review," sends an approval request email to the reviewer with the post content
• When the reviewer replies with "approved" (or clicks an approval link), updates the status in the sheet
• Optionally, sends approved posts to Buffer or a social media scheduling tool
• Tracks all posts and their statuses in the master sheet

Tools needed (all free tier)

Google Sheets, Make or Zapier, Gmail, Buffer (free tier, optional).

Skills this demonstrates

Approval workflows, status tracking, email-based interactions, integration with scheduling tools, and managing a process across multiple people.

How to document it

Show the Google Sheet template you designed. Walk through the approval flow with screenshots. Demonstrate a post moving from "draft" to "approved" to "scheduled." Explain how this eliminates the scattered WhatsApp approval process.

Project 5: Event or appointment booking system

The problem it solves

A service provider (salon, clinic, tutor, consultant) manages bookings manually. Clients call or message on WhatsApp to book, the provider checks their calendar, suggests times, and confirms. Double bookings happen. Time is wasted on back-and-forth scheduling.

What you build

An automation that:

• Provides a booking form (Google Form or Calendly) where clients select their preferred service, date, and time
• Checks against existing bookings (in a Google Sheet or Google Calendar) to prevent conflicts
• Sends a confirmation email to the client with booking details
• Adds the booking to the provider's Google Calendar
• Sends a reminder to both the client and provider 24 hours before the appointment
• Logs all bookings in a tracking sheet

Tools needed (all free tier)

Google Forms or Calendly (free tier), Google Calendar, Google Sheets, Make or Zapier, Gmail.

Skills this demonstrates

Calendar integrations, conflict checking, reminder scheduling, client-facing systems, and end-to-end service automation.

How to document it

Create a walkthrough showing a client booking from start to confirmation. Show the calendar entry being created automatically. Demonstrate the reminder system. If you build this for an actual service provider, their feedback is powerful portfolio material.

How to present all five projects together

Create a simple portfolio page

You do not need a custom website. A clean Google Doc, Notion page, or free Carrd site works. For each project, include the project name, the problem it solves, tools used, a screenshot of the automation flow, and a link to a brief video walkthrough if you made one.

Lead with the business problem

When presenting to potential clients or employers, start with the problem each project solves, not the technical details. "I built a system that makes sure no customer inquiry goes unanswered for more than five minutes" is more compelling than "I built a five-step Zapier automation with conditional routing."

Keep projects updated

If a tool changes its interface or you learn a better approach, update the project. A portfolio with outdated screenshots looks neglected. Our course, AI and Automation for Beginners, includes hands-on projects that can supplement these five.

FAQ

Can I use these exact projects in my portfolio?

Yes. Adapt them to your specific context (use a real or realistic Kenyan business scenario), but the project structures above are common automation patterns that employers and clients recognize. The value is in your execution and documentation, not in the uniqueness of the concept.

What if the free tier limits restrict what I can build?

Free tiers on Make and Zapier limit the number of tasks or scenarios you can run monthly. For portfolio purposes, you only need to demonstrate that the automation works, not run it at production scale. Build it, test it, document it, then pause or delete it if you hit limits. The documentation is what goes in your portfolio.

Should I build these for real businesses or use sample data?

Real businesses are always better because you get genuine feedback and a potential testimonial. If you cannot find a willing business, use realistic sample data. A booking system for a fictional "Nairobi Hair Studio" with realistic services and pricing is still a strong portfolio piece, especially if the automation itself works end to end.

How long does it take to build all five projects?

If you already know a no-code platform, plan for two to four hours per project. If you are learning as you go, expect four to eight hours each, including time spent watching tutorials and troubleshooting. Building all five over two to four weekends is a realistic timeline for most people.