Tunde Godfrey / Creator

Creator

I build with AI: courses, tools and prompt books that help people do real work faster.

I like knowing how things work, and then putting that knowledge to use. With AI, that has meant building.

I created an NGO management system for YCDI that runs its chapters, members, KPIs and permissions. I've made more than 50 reusable Claude skills, written courses on using Claude for communication professionals, and developed a training manual on building applications with Claude. I've also written prompt books for graphic, UI and UX, and cartoon and motion designers, and for founders.

More about my background

I'm picky about the tools I put my name on. The best ones take the tedious part of someone's work and hand back the time for the part that needs a human.

I keep it practical, and I work with companies and young people who want to use AI properly.

Built
An NGO management system for YCDI
Made
More than 50 reusable Claude skills
Wrote
Courses on using Claude for communication professionals
Wrote
Prompt books for designers and founders

Apps I've built

Web app | Free to use

Solfa Harmoniser

What it does

A free tool that takes a melody in tonic sol-fa and harmonises it in four parts: soprano, alto, tenor and bass.

Try it

Try it here. Put in a melody and it writes the four-part harmony.

Web app | In development

YCDI Programme Hub

What it does

A private intranet I built for YCDI. It follows a programme from approval to report, and keeps participants, volunteers, safeguarding, finance, communication and the Board's figures in one place.

The problem

A youth organisation with chapters in many places runs programmes in schools, works with young people and volunteers, handles donations and answers to a Board. Without one trusted record, programme approvals sit in chat threads, reports arrive in different shapes, safeguarding checks are hard to follow, and the Board's figures have to be assembled by hand.

My design reasoning

I started from who decides what. The national team approves programmes, chapter coordinators report on them, and a few people see money and safeguarding records, so every screen is built around a role and what that role needs to do next.

Two choices shaped the rest. The home screen puts the programmes waiting for a decision first, with one button each. And anything sensitive leaves a trail: safeguarding entries record that something moved and who moved it, never what it was about, and every change to access, targets and volunteer records goes into an audit log.

The phone matters as much as the desktop, because coordinators work from schools and venues. So the phone version has five tabs for the things used every day, and a More menu that holds everything else.

The solution I developed

Twenty-eight screens, grouped the way the work is done. Programmes: the national overview and approval, reports, and attendance registers. People: participants on a five-stage discipleship pathway, the volunteer register and applications, finance (claims, stipends, grants, donations, the annual budget) and a directory. Spiritual life: the ministry framework and the prayer manual. Communication: calendar and notices, messaging, documents, content for review, audience and email campaigns. Safeguarding and compliance: safeguarding, declaration renewals, the Board and funder KPI report and data protection. Administration: admins, the audit log and each person's profile. The demo above has all of them, on a desktop or a phone.

Screens

Swipe sideways to see the whole screen.

OverviewThe home screen: key numbers, the programmes that need a decision, and students by chapter.

Swipe sideways to see the whole screen.

Programme OperationsEvery programme with its status, and a review screen for each one.

Swipe sideways to see the whole screen.

Participants & DiscipleshipYoung people on a five-stage pathway, with anyone who has not been contacted lately flagged.

Swipe sideways to see the whole screen.

Volunteer RegisterEveryone across the organisation, with their volunteer record and next step.

Swipe sideways to see the whole screen.

Board & Funder KPIsEach quarter's targets against actuals, worked out from the app's own records.

How people move through it

  1. Start on the home screen: the four numbers, then the programmes that need your attention, each with a Review button.
  2. Open a programme to see its date, size, budget and venue, who is running it and three readiness checks, then approve it or ask for changes.
  3. Follow up on people: the participants list shows who has not been contacted lately, and the volunteer register shows who is still onboarding.
  4. Keep the money and the rules in view: claims, stipends, grants, donations and the annual budget, with safeguarding clearances and declaration renewals beside them.
  5. Prepare the Board paper: pick a quarter on the KPI report, compare each target with the actual, and download the table.
  6. On a phone, use the five tabs for daily work and the More menu for everything else.

What I learned

  • Building in small batches and testing the database after each one, including mutation testing, made each stage easier to trust before the next began.

Impact

Still in development, so there are no results to report yet. The aim is for national and chapter teams to work from one record, and for the Board's figures to come from what the app holds rather than from spreadsheets assembled by hand.

Built with

  • React
  • Vite
  • Supabase

It was built in batches, and the database was tested at each stage, including mutation testing.

Web app | In use

Media Monitor

What it does

A media monitoring tool for communications teams. It reads the day's press, scans the web for mentions, follows sentiment and share of voice, and flags early signs of a crisis.

The problem

Communications teams often follow the press by hand: opening one outlet after another, searching for mentions and judging tone from memory. It is slow, it depends on who happens to be looking, and early signs of a problem are easy to miss.

My design reasoning

I treated it as a morning routine and a warning system rather than a report. The first screen shows the four numbers a communications lead asks for: mentions, sentiment, share of voice and crisis level. Each opens its own screen.

Risk is shown as a word with the stories behind it, so the number is never a mystery. Anything that searches the web takes a while, so every screen has a clear loading state and a way to run it again. Limits on how often a scan can run keep costs predictable.

The solution I developed

A set of screens that run from the day’s press review to a crisis check: a dashboard of four numbers, a daily press review with suggested actions, mentions and web scans by business unit, sentiment and themes, competitors and share of voice, narratives, crisis signals with an action plan, who is writing on your sectors, spokespeople, weekly and monthly briefings, and a settings page that tells it what to look for. The demo above shows every screen.

Screens

Swipe sideways to see the whole screen.

Mention ScanA live web search for mentions of the organisation and each business unit, counted by business unit and website.

Swipe sideways to see the whole screen.

Crisis SignalsAn overall risk level with the stories behind it, so the team can see what needs attention first.

How people move through it

  1. Open the dashboard. Four numbers show where the day stands, and two short readings explain the leading story and the wider industry signal.
  2. Run the press review. Stories are grouped by topic, each with a suggested action for the team.
  3. Check mentions and sentiment. Filter by tone and see which themes push the score up or down.
  4. Compare with competitors by mentions, sentiment and share of voice.
  5. Open crisis signals. If the level rises, the screen lists the stories behind it, an action plan and the words to watch.
  6. Generate the weekly or monthly briefing to share.
  7. Adjust settings to change what the tool looks for.

What I learned

  • Live searches are slow, so a loading state and a way to run again matter as much as the result itself.
  • Costs follow use. Limits on how often a scan can run keep spending predictable.
  • A tool is only used if people know how to use it, so I produced a training handbook and a knowledge-sharing deck alongside it.

Impact

The communications team has one place to follow coverage, tone, competitors and early risk. I produced a training handbook and a knowledge-sharing deck so colleagues could learn it. Figures from real use are internal and are not published here.

Built with

  • React
  • Vite
  • Node.js
  • Express
  • Claude API

It sits behind a login, so the live tool stays private.

Certifications and training

Start with what you need

Websites and AI work, built to be used by people who are not technical.

Website for your business or organisation

A site you can edit yourself without code, that says clearly what you do and how to reach you.

Up to five pages, a simple editor for your own updates, a contact route, and basic search set-up. Hosting costs are explained before we start.

Takes
Three to four weeks
How
Done for you

Request a websiteSee scope and price for Website for your business or organisation

Website for your business or organisation

A site you can edit yourself without code, that says clearly what you do and how to reach you.

Up to five pages, a simple editor for your own updates, a contact route, and basic search set-up. Hosting costs are explained before we start.

Takes
Three to four weeks
How
Done for you

Request a websiteSee scope and price for Website for your business or organisation

AI automation for one workflow

One repetitive job in your work that a tool now does for you, scoped properly before anything is built.

A paid scoping call, a written plan with a fixed price, the build, and a short handover.

Takes
Depends on the scope
How
Done for you

Request an automationSee scope and price for AI automation for one workflow

Mobile app

A simple app on one platform, scoped carefully so you know what you are paying for.

A paid scoping session, a clear list of what is in and out, a fixed quote, then the build.

Takes
Depends on the scope
How
Done for you

Discuss an app ideaSee scope and price for Mobile app

Claude training for your team

Your team learns to use Claude for real work in their own roles.

A half day session built around your team's actual tasks, practice time, and a short take-home guide.

Takes
Booked by date
How
Booking

Book team trainingSee scope and price for Claude training for your team

See prices for all Creator services

Build with me

My resources page will list my courses and prompt books. For something specific to your team or programme, write to me.

Where to next?

The other roles