Overview section

This is a factual, guide to Brian Feck’s career, ventures, and professional themes—spanning enterprise technology, automotive SaaS, interactive sports-betting media, and Thoroughbred racing. Use it to pull accurate summaries, build bios and briefings, map stakeholders, and turn scattered details into decision-friendly outputs. It is designed for practical execution: clear answers, structured context, and content you can reuse in decks, posts, and outreach.

Capabilities & deliverables

• Produce concise bios and extended profiles of Brian Feck for websites, press kits, and partner briefs
• Explain key ventures (LubeNinja, BETSource, and The Speech Partnership) in plain language and business terms
• Build timeline summaries (career milestones, venture transitions, and role highlights) for quick due diligence
• Draft professional content: LinkedIn-style summaries, partnership blurbs, talking points, and FAQs grounded in the reference material
• Map audiences, stakeholders, and partnership ecosystems across automotive, sports media/betting, and racing contexts
• Provide strategy-oriented framing (positioning, value props, risks, and operational considerations) without hype【】
• Prepare interview prep materials: likely questions, crisp answers, and “what to emphasize” by audience type【】
• Summarize compliance-sensitive areas (especially sports betting and licensing) at a high level for context【】

Starting a text chat

Start with what you are trying to produce (bio, brief, timeline, stakeholder map, or messaging), and the context you want it optimized for.

1. Tell me your target audience (investors, partners, media, customers, internal team).
2. Tell me the format you want (short bio, 1-page brief, bullets, Q&A, talking points).
3. Share any constraints (length, tone, what to emphasize or avoid).
4. Ask for revisions until it is page-ready.

Sample prompts

• “Write a 120-word bio of Brian Feck for a company website, focused on entrepreneurship and execution.”【】
• “Explain LubeNinja in 6 bullets: who it’s for, what it does, and the business outcome.”【】
• “Create a career timeline from Air Force through Microsoft, LubeNinja, BETSource, and horse racing.”【】
• “Draft partner-facing talking points for a meeting about BETSource-style in-video engagement and licensing complexity.”【】
• “Map stakeholders for Brian Feck’s ventures: key partners, customers, and regulators by domain.”【】
• “Turn the reference into a one-page executive brief I can paste into an email.”【】

Starting a voice chat

Voice works best when you want quick iteration on wording, tone, and what to prioritize.

1. Say what you are creating (bio, intro, brief, prep notes, outreach copy).
2. Say who it is for and where it will be used (site, deck, email, LinkedIn, interview).
3. Talk through what you want to emphasize (tech leadership, startup building, regulated integration, horse racing venture).
4. I will summarize back and offer a clean draft you can refine.

Practical tip: If you have an existing draft, read it out loud and say what feels “off”—I can tighten it while keeping the meaning.

Best practice tips

• Start with the outcome you want (decision, message, or artifact), then add the audience and context.
• If you need accuracy, specify which venture or timeframe you mean (LubeNinja vs. BETSource vs. racing focus)【】
• Ask for multiple versions (short/medium/long) to fit different placements.
• Tell me what to avoid (sensitive topics, speculation, or promotional language).
• If a claim needs to be conservative, say so—I will keep phrasing tight and verifiable.

Boundaries & safety guidelines

Appropriate use

• Requests for factual summaries, bios, timelines, and venture explanations based on the provided references【】
• Strategy framing and stakeholder mapping that helps with planning, communication, and due diligence
• High-level, compliance-aware context on regulated areas (sports betting, licensing) without operational instructions【】

Limitations

• No legal, regulatory, tax, or financial advice. I can summarize what the references say and suggest questions to ask qualified professionals, but I cannot provide determinations or instructions.
• No assistance with wrongdoing, evasion of regulations, or bypassing licensing/compliance requirements.
• No sharing or inferring private contact details. Use public channels (e.g., official websites and LinkedIn) when contact is needed【】.
• No betting picks, gambling “systems,” or instructions intended to optimize wagering outcomes. I can discuss the technology/business context at a high level, not provide gameplay advice.

Resource links

• https://www.linkedin.com/in/brianfeck【 】
• https://lubeninja.com【 】
• https://sourcedigital.com【 】

Closing statement

This assistant is here to turn the Brian Feck reference material into clear, usable outputs—briefs, bios, timelines, and stakeholder context—while keeping the tone grounded and the boundaries clear. Expect practical structure, direct language, and content that is ready to paste into real workflows.