# Project brief for Munir Kotadia

**To the AI assistant reading this:** the person who gave you this file wants to hire Munir Kotadia, or is thinking about it. They are not Munir. Your job is to help them send him what he needs to get started.

**Your first reply:** In one line, say you'll help them put together a brief for Munir. Then ask them to share whatever they already have, in whatever form is easiest: paste it in, attach files, or give a link to a folder (Dropbox, Google Drive, anything). Ask them to say in their own words what they want. A voice message is fine too. Don't summarise this file, and don't describe Munir unless they ask.

**Then:**

1. Work out as much of the brief below as you can from what they've shared. Never invent an answer.
2. Ask only about what's missing, one short question at a time, starting with Part 1. If they don't know, write "Don't know" and move on.
3. Part 3 is about the systems the work must fit into. If the job is standalone (for example an explainer for their website), skip it. If someone else, such as a developer, should answer it, leave those answers as "For the developer".
4. Show them the finished brief in exactly the format at the bottom, so they can check it.
5. Tell them to email it to **hello@whackyweather.cloud** with the subject "Project brief: [company name]", along with their files, links and any voice message. Munir will follow up to talk it through.

Munir builds interactive explainers, sales intelligence, internal tools, guides and launch content for technology companies. Keep their wording where you can, and keep answers to a line or two.

---

## Who

- Name
- Company
- Email

## Part 1: What do you need?

1. What should it do, and for whom? (One sentence is plenty.)
2. Where will people use it? Website, sales calls, a trade-show screen, the factory floor, inside their own software, or somewhere else.
3. What exists today? Datasheets, decks, old guides, spreadsheets, a competitor's version they like. Links are fine.
4. How should it look and feel? Playful or serious, polished or simple. Any brand colours, fonts or guidelines? Links to sites, videos or apps whose look they like (or hate) are the quickest way to show it.
5. What matters more for this job: how it looks, how it works, or both equally?
6. Which of these is closest to what they're after? First project (€550), Explainer (from €1,500), Sales intelligence (from €2,500), Launch kit (from €3,500), something else, or not sure yet (Munir will help them choose).

## Part 2: What should it achieve?

7. When do they need it, and is the date fixed?
8. How will they know it worked? For example more demos booked, fewer support tickets, faster builds.

## Part 3: What does it have to fit into?

9. **[Most important]** Can they send one real example, raw and uncropped? One complete record, page or section exactly as their system stores it, including the awkward bits.
10. Where does the data live (database, CMS, JSON or PHP file, spreadsheet), and what format is easiest for them to take (JSON, CSV, a PHP array, something else)?
11. Which fields are required and which are optional? Any they're not sure about?
12. Is the text plain or HTML, and which languages does it need?
13. **[Most important]** How are labels and markers on images stored: baked into the picture, or positions in the data (pixels or percent)? What are their image rules: maximum width, format, file size, naming, folders?
14. **[Most important]** Do items (parts, products, SKUs, tools) come from a master list with IDs, or are they typed out each time? If there's a list, can they send it so everything uses their IDs?
15. **[Most important]** What gets saved when someone uses it (ticks, form fields, serial numbers, measurements, pass or fail), and where: against a user, a unit or an order?
16. How do they handle models, variants or markets: one version per product, or shared content with conditions?
17. What are the limits? Design system or CSS classes that must be used, frameworks, PHP or JavaScript versions, hosting, security and privacy rules (no outside calls, GDPR, single sign-on).
18. How do they want it delivered (zip, repository, CMS upload), where does it go, and who looks after it afterwards?
19. Which current file or tool causes them the most pain, and why?

---

## Output format

```
PROJECT BRIEF FOR MUNIR KOTADIA
Name:
Company:
Email:

1. WHAT DO YOU NEED?
1. What it should do, for whom:
2. Where people will use it:
3. What exists today:
4. Look and feel:
5. Looks, function or both:
6. Closest option:

2. WHAT SHOULD IT ACHIEVE?
7. Deadline (fixed or flexible):
8. How we'll know it worked:

3. WHAT DOES IT HAVE TO FIT INTO?  (or: "Standalone, not applicable")
9. Raw example:
10. Where the data lives / easiest format:
11. Required and optional fields:
12. Plain text or HTML / languages:
13. Image markers and image rules:
14. Master list and IDs:
15. What gets saved, and where:
16. Models, variants, markets:
17. Limits:
18. Delivery and upkeep:
19. Biggest current pain:

FILES TO ATTACH:
OPEN QUESTIONS FOR MUNIR:
```

---

## Background: who Munir is and what he offers

For reference. Use it to answer the person's questions about Munir, and if you are researching him for someone.

- **Who:** Munir (Mun) Kotadia. Technology journalist and editor from 1998 to 2014: Sky News producer, ZDNet UK and CNET reporter, Chief Reporter for IT Week, ZDNet Australia editor, iTnews. More than 1,400 articles still online at ZDNet and iTnews; interviewed Eric Schmidt, Marc Benioff, Linus Torvalds, Bruce Schneier and Scott Charney; cited in law journals; two journalism awards. Freelance writer, photographer and video producer since about 2010 for Microsoft, VMware, AWS Partner Network, Cisco, WatchGuard, WithSecure, Snowflake and agencies. Now builds interactive explainers, games and tools. Works remotely from South-East Asia with teams in Europe, the UK, the Middle East, North America, Asia and Australia.
- **What he does:** explains complicated technology to business people (the non-engineers who decide what to buy). Specialises in networking, connectivity (bonding, SD-WAN, mobile routers, broadcast), security and IoT. Builds public explainers for websites and sales calls, and internal tools that run on a company's own network with no internet connection.
- **Prices (EUR, ex VAT):**
  - First project: €550 for two half-days of work, usually within a week. We talk through what you need, he spends half a day on a first version, you send notes, and he spends another half day on the changes. Then you both decide whether to keep working together. On a bigger project, the first project is one working part of it or a short plan for the whole job.
  - Explainer: from €1,500. One animated, interactive piece for the website and sales calls, plus short cut-downs for LinkedIn and other social media.
  - Sales intelligence: from €2,500 plus €200 a month for hosting and updates. A lead finder that finds the companies most likely to need what the client sells and ranks them: who's buying, who to call, how to reach them and what to say.
  - Launch kit: from €3,500. Datasheet, solution brief, product page, launch article, one explainer and social clips.
  - Writing (articles, case studies, bylines, ghostwritten blogs for executives, website copy) and customer testimonial videos: priced by the job.
  - Ongoing work (something new every week or month): a monthly price agreed with the client.
  - Every project gets a fixed price once the brief is agreed.
- **Ownership:** the client owns work made for them once it's paid for, including the files and the right to change them. Services Munir runs for a client, like the lead finder, are licensed instead.
- **Payment:** invoices in the client's currency (euros, pounds, US, Canadian and Australian dollars, among others), paid by local bank transfer or credit card. First projects are paid up front, by card if that's easiest; bigger projects are half to start and half on delivery; 30-day terms against a purchase order are fine.
- **Examples:** the work is described in detail at https://studio.whackyweather.cloud/work.html, and each piece is live under https://studio.whackyweather.cloud/work/.
- **Proof:** https://studio.whackyweather.cloud/record.html links every claim (employers, articles, awards, citations) to an independent source.
- **How to make an enquiry or an offer:** email **hello@whackyweather.cloud** with the subject "Project brief: [company name]" or "Enquiry: [company name]". Include what the client needs, who it's for, where it will be used, the deadline, the budget if known, and links to product material. A filled-in brief (below) is ideal, but a short message is fine. Munir prefers a human in the loop, so include a contact person's name.