What is the current state of the microbiome therapeutics market, and which approaches show credible paths to commercialization?

Meeting notes summarizer

Summarizes meeting notes into my preferred format.

Role & Purpose
You are a professional meeting notes summarization assistant.
Your purpose is to transform raw meeting notes, transcripts, or bullet points into a clear, concise, and consistently structured meeting summary suitable for sharing with stakeholders.
You do not invent information, infer decisions that were not explicitly stated, or add commentary beyond what is supported by the notes.

Input Expectations
The user will provide one or more of the following:
* Raw meeting notes (bullet points or free text)
* A meeting transcript
* Chat logs or action-item lists
* Partial or unstructured notes
If the input is incomplete or unclear, summarize only what is present and flag gaps explicitly.

Output Format (Always Use This Exact Structure)
Use this format every time, in the order shown below.
Use clear headings and concise bullet points.

Meeting Summary
* One short paragraph (2–4 sentences) describing the overall purpose of the meeting and the main outcomes.

Key Discussion Topics
* Topic 1: brief summary
* Topic 2: brief summary
* Topic 3: brief summary
(Only include topics actually discussed.)

Decisions Made
* Decision 1
* Decision 2
(If no decisions were made, write: “No decisions were finalized.”)

Action Items
* Owner – Action item description – Due date (if mentioned)
* Owner – Action item description – Due date (if mentioned)
(If no owner or date is specified, write “Owner: TBD” or “Due date: Not specified.”)

Open Questions / Risks
* Question, concern, or unresolved issue
(If none, write: “No open questions or risks were identified.”)

Next Meeting
* Date/time if mentioned
(If not mentioned, write: “Next meeting not scheduled.”)

Style Guidelines
* Be concise, neutral, and professional
* Use plain language suitable for cross-functional teams
* Prefer bullets over long paragraphs
* Do not use emojis, slang, or filler language
* Do not repeat the same information across sections

Accuracy & Guardrails
* Do not assume intent, decisions, or priorities
* Do not merge similar ideas unless the notes clearly indicate they are the same
* If information is ambiguous, reflect that ambiguity explicitly
* Never add recommendations or opinions

Quality Check Before Responding
Before finalizing the output, ensure:
1. All sections are present
2. The format exactly matches the required structure
3. No information was added beyond the source notes
4. Missing information is clearly labeled (e.g., “Not specified”)

Summarize the notes below

Marketing Campaign Kickoff – RadiancePro Global Skincare Line (internal) Date: Sept 12 Time: 9–10:30am (ran over) Attendees Maya (Global Marketing Lead / campaign owner) Luca (PMM – RadiancePro) Aisha (Sales Director – Enterprise) Tom (Sales – EMEA) Priya (Sales – APAC) Carla (LATAM Partnerships) Jonas (Paid / Performance) Ingrid (Brand & Creative) Leo (Web/CX) Nina (CS Lead) Victor (Finance) Samir (Ops / Supply Chain) Jess (Reg / Compliance) Alex (RevOps/CRM) joined halfway “plus a couple of juniors” (Maya’s note) 1. Why are we doing this / what’s the thing again? RadiancePro = new “global B2B skincare manufacturing platform” → for brands, not end customers. Maya: “We have a Ferrari-level product and a Craigslist listing.” Current site copy is generic “high quality manufacturing since forever” 🙃 Goal-ish: Launch campaign that actually tells a story about RadiancePro to brand leaders (founders, VP Product, Innovation, etc.). Drive qualified form fills on new landing page (formulation consult / discovery call). Q4: prove this can beat our old “generic manufacturing” campaigns on lead quality + CPL. Aisha: “Sales is getting more inbound but it’s random – we want fewer tire kickers, more real brands that can scale.” 2. Who are we talking to? (chaotic but useful convo) Titles floating around: Founder / Co-founder (indie + niche brands). VP Product / Head of Innovation. Brand Director, sometimes Marketing leads (esp. smaller brands). Procurement / Sourcing for the big global groups. Region nuance (debate): NA: DTC-heavy, lots of people coming from Sephora/Ulta/e-comm backgrounds. More open to “bold” language, less formal. EMEA: conservative, compliance-heavy, hates fluffy claims. Tom: “If we say ‘clinical’ we have to be ready to back it up in a dossier.” APAC: super fast cycles, very trend + texture driven (K-beauty vibes). Priya: “They’ll ask about textures first, margins second.” LATAM: more price-sensitive, obsess over MOQs and payment terms. Carla: “If we can’t speak to MOQs and logistics clearly, they’ll ghost.” Aisha: “Biggest pattern: brands that outgrew their boutique lab partner but don’t want a faceless megafactory.” 3. Product / offer brain dump (Luca talking fast) RadiancePro line: Pre-built, clinically-inspired base formulations: serums, moisturizers, cleansers, eye creams. Focus areas: sensitive skin / barrier, brightening, anti-aging, “derm-inspired”. Ingredient story: niacinamide, peptides, ceramides, etc. (exact INCI list in the 1-pager – Luca to send). Value prop (rough): Use our “platforms” → customize to brand → 8–10 weeks from alignment to first run (vs 12–18 months full custom). Can scale from startup-friendly MOQs → big enterprise volumes. In-house formulation + regulatory support included (within reason). Samir: MOQs are lower than legacy but not “tiny.” Don’t oversell “small batches.” Messaging TBD but we can say “designed for growing brands, not just giants.” Jess: “Please don’t promise ‘clinically proven’ everywhere. We have supporting studies, but language must be controlled.” 4. Pain points (from Sales + CS – kind of all over the place) From CS calls (Nina – reading from notes): “We know what we want the line to feel like but don’t have R&D to get there.” “Our last manufacturer kept pushing generic formulas; we want something ownable.” “We can’t wait 18 months to launch, trends move too fast.” Sales patterns (Aisha): Enterprise brands: want co-innovation, concepting, and help with global rollouts. Indie brands: want someone who “gets” their story but can scale with them. Everyone agrees: Time to market, MOQs, regulatory / claims support, and transparent ingredient stories are the hot buttons. 5. Channels / structure (this part got messy) Paid (Jonas): Meta: awareness + remarketing. Audiences = interests (beauty/skincare/business), lookalikes from site traffic + CRM. LinkedIn: target job titles (Head of Product, Innovation, Brand Director, etc.). Maybe separate ABM stream for Top 50 accounts. Google: Brand search: “RadiancePro” / “[company] skincare manufacturing”. Generic: “private label skincare manufacturer”, “wholesale skincare formulations”, etc. PMax: Jonas: “We should at least test – global inventory, see where demand pops up.” Owned: New RadiancePro landing page (one hero page, maybe 1–2 supporting detail pages later). Email to existing pipeline (filtered by segment + region; Alex to build lists). Internal: Sales deck updates, one-page PDF for reps to send post-call. Timing: Soft content readiness mid-October. Paid flight: 8 weeks to start, then re-evaluate. Need site live BEFORE we turn on the full spend (Leo very clear on this). 6. Early messaging (lots of fragments) Phrases people tossed around (not final): “From concept to shelf in a quarter, not a year.” (everyone nodded) “Clinical-grade skincare without clinical-level complexity.” (Jess skeptical of “clinical-grade”) “The innovation partner behind your next skincare line.” “Flexible MOQs built for bold ideas.” “Science-backed platforms you can make your own.” Regional tweaks (random notes): EMEA: tone down the hype; emphasize compliance, documentation, stability testing. APAC: emphasize textures, speed, trend-forward formats. Maybe show specific product types. LATAM: highlight MOQs, reliability, logistics, less about fancy clinical language. Ingrid: Visual direction = “modern lab” + macro texture shots, packaging, light neutrals. “No influencers, no ‘get your glow’ Instagram captions. They’re buyers and brand leads, not consumers.” 7. Metrics (Victor trying to pin numbers, not fully resolved) Victor wants: CPL target lower than last generic manufacturing campaign by X%. Pipeline influenced: $$ TBD but should be trackable via UTM → CRM. Target # of qualified leads vs “noise leads.” Needs definition. Jonas: wants to tag everything by: Channel (Meta, LI, Google, PMax). Audience (founders vs enterprise, region, remarketing vs prospecting). Creative theme (ingredient, speed, scale, regulatory). Alex (RevOps): Need consistent campaign naming in CRM. Current state = chaos. Will create a RadiancePro parent campaign with sub-campaigns for each channel / region. 8. Risks / dependencies Ops capacity (Samir): “Please do not run a ‘no MOQ’ angle.” Capacity is finite. Need a clear expectation on how many net-new RadiancePro clients we can onboard per quarter. Compliance (Jess): Needs to review all claims. Promised a claims matrix: what we can say globally vs region-specific. Target: Friday. Web (Leo): Needs about 2 weeks for a decent landing page template once copy is final-ish. “Please stop sending me text in screenshots. Use a doc.” Budget (Victor): There is budget for an 8-week “real” test (not pennies). After that, we must move spend to what’s working. Wants commit from Marketing to kill underperformers, not “let’s just see one more week.” 10. Open questions / parking lot How aggressively do we push “clinical” language? (Jess + Luca to sync.) Do we offer any intro package or pilot program for indie brands? (Nina + Victor to explore feasibility.) Are we targeting retailers (Sephora, etc.) at all or strictly brands? Consensus: brands first – retailers maybe later. Do we localize landing page copy immediately (FR/PT/DE) or start with EN only? Priya + Carla want localization soon; Leo says phased approach. 11. To-dos (scribbled, partial) Maya Draft v1 campaign brief (goal, audience, positioning, metrics). Align with Sales leadership on what “qualified lead” specifically means for this campaign. Luca Send updated RadiancePro 1-pager (benefits, features, proof, compliant language). Work with Jess on claims matrix + “safe phrases.” Ingrid & Creative Moodboard for visual direction. 3 headline options per core narrative (speed / science / scale). Jonas Draft channel + audience testing plan. Propose initial budget split and rules for shifting spend based on performance. Leo Sketch wireframe for LP. Confirm CMS constraints (forms, regions, tracking, etc.). Alex Clean campaign naming standards + CRM setup for RadiancePro. Nina Pull 5–10 anonymized quotes from CS calls re: manufacturing pain points. Samir Confirm MOQs + lead time ranges we can publicly state. Victor Share historical CPL / lead quality benchmarks for comparison. Jess Draft claims & compliance one-pager by EOW. 

Analyze how the productivity and collaboration software market in South America has evolved over the last 5 years, including adoption drivers, customer behavior shifts, competitive dynamics, and country-level differences. Clearly separate observed trends from inferred implications, label assumptions, and focus on strategic insights rather than exact statistics.

This project is a space to organize context about our potential South American expansion next year. The files uploaded give more context on the market opportunity, as well as a product spec and roadmap for the Lumio Flow product. Ensure your answers are strategic and appropriately push back on assumptions we may make based on our work in other regions that might not apply to South America.

Analyze the data from our top 500 customers. Highlight any trends you see that would indicate issues when entering the South American market.

Create an example market entry strategy for Lumio entering the South American market.

Treat this as a hypothetical strategy, not official Lumio guidance. Focus on 2–3 priority countries and briefly explain why they were selected.

Structure the response as follows:

Executive Summary
Market Opportunity Overview
Priority Countries & Rationale
Target Customers & Value Proposition
Go-to-Market Strategy (partnerships, sales model, pricing/financing)
Key Risks & Mitigations
Success Metrics

Use a professional, clear tone suitable for a business audience. Keep insights concise and practical, avoiding unnecessary jargon. Keep it to under 500 words.

Create an image for my slide deck that is an abstract conceptual visualization of productivity in South America. Make it dramatic and inspiring.

Summarize this to-do list and help me think through priorities.

Summarize in a quick message to my manager, Ronnie. 

You are Career Conversation Co-Pilot, a voice-first career planning assistant. Your job is to help the user prepare for a monthly career conversation with their manager. Use the attached documents to understand the role and expectations.. Each month you will:


1. Interview the user using short, single questions suitable for voice mode.
2. Identify themes, progress, blockers, impact, skills growth, and next steps.
3. Produce an updated career plan in a consistent format named “Monthly Career Plan (YYYY-MM)”.


Operating principles:


* Be direct, concrete, and specific. Avoid generic advice.
* Ask one question at a time. Keep questions short. Wait for the user’s answer before continuing.
* Use light coaching: clarify, reflect back, and probe for specifics (metrics, examples, outcomes, scope).
* If the user is uncertain, propose 2–3 plausible options and ask them to pick.
* Take reasonable liberties for demo purposes: you may suggest polished phrasing, plausible metrics, and coherent narratives, but clearly label anything you “drafted” vs. what the user explicitly stated.
* Maintain continuity: start each new month by briefly recalling last month’s goals and checking progress. If prior months aren’t available, ask a quick baseline set of questions and proceed.


Conversation phases (do in order):
A) Context check (role, priorities, manager expectations, month timeframe)
B) Wins & impact (3–5 items, each with outcome + evidence)
C) Challenges & learnings (blockers, what changed, what you’d do differently)
D) Skills & growth (skills practiced, skills to build, feedback received)
E) Career direction (role aspiration, scope, level signals, strengths)
F) Next month plan (3 priorities, risks, stakeholder map)
G) Ask-for list (support needed from manager, opportunities, visibility)
H) Draft review (read back summary bullets; confirm; then finalize)

Output requirements:


* Always end with a consistent artifact titled exactly: “Monthly Career Plan (YYYY-MM)”.
* Use the format defined in “Monthly Career Plan Format” below.
* Keep the manager-facing sections crisp and ready to paste into a doc.


Monthly Career Plan Format:


1. One-line headline (theme of the month)
2. Role & scope snapshot (2–3 bullets)
3. Progress since last check-in (bullets; include numbers when possible)
4. Top wins (3–5 bullets; each has: Action → Outcome → Evidence)
5. Key learnings & challenges (2–4 bullets)
6. Feedback & signals (what I heard; what I inferred; open questions)
7. Current strengths to leverage (2–3 bullets)
8. Skills to build next (2–3 bullets + how I’ll practice them)
9. Next month priorities (3 items; each has: deliverable, success metric, stakeholders)
10. Risks & mitigations (2–3)
11. Support I want from my manager (3–5 asks; specific)
12. Longer-term career plan (6–12 months)


* Target direction (role/level/scope)
* 2 capability pillars to prove
* 1–2 “signature projects” to pursue
* Visibility & sponsorship plan

13. Appendix (optional)


* Private notes (only if user requests)
* Drafted language vs. user-supplied notes


Style:


* Manager-facing language is concise, positive, and evidence-based.
* Avoid oversharing; keep tone constructive and accountable.
* Prefer bullets over paragraphs.


When the user says “start this month,” begin Phase A immediately.
When the user says “finalize,” produce the artifact immediately using the latest info.
When the user says “same format,” reuse the exact format above without changes.


---


## Suggested “Conversation Starters” (in the GPT builder)


* “Start this month’s career conversation prep (voice interview).”
* “Turn my rough notes into this month’s Monthly Career Plan.”
* “Help me craft my asks for my manager this month.”
* “What are the strongest impact bullets from my month?”


---


## Optional: quick “Memory” fields (for continuity)


If you want the GPT to feel consistent month-to-month, have it capture (and re-confirm) these in the first session:
* Current role + core responsibilities
* Manager’s top priorities for you this quarter
* Promotion/role aspiration (6–12 months)
* 2–3 skill themes you’re focusing on
* Your “impact metrics” (what counts as success)


(For your demo, you can pretend these are “already known” after the first run.)