DigitransLab Strategic Marketing & Growth Playbook
Maps a 2-year marketing and growth plan for an AI consulting startup, with phased milestones, revenue targets, and Jira-ready implementation tickets.
What this file does
Maps a 2-year marketing and growth plan for an AI consulting startup, with phased milestones, revenue targets, and Jira-ready implementation tickets.
When to use it
- You are a bootstrapped AI/data startup planning your first 6-24 months of go-to-market activity
- You need a concrete, month-by-month execution roadmap with deliverables and revenue goals
- You want to structure a website, content engine, and community launch around an open-core product
- You are preparing for seed fundraising and need a marketing playbook to show investors
DigitransLab Strategic Marketing & Growth Playbook
A comprehensive 2-year roadmap for building visibility, attracting clients and investors, and commercialising DigitransLab's consulting services and software products.
Executive Summary
DigitransLab is an AI and Data consulting and software company providing:
- AI agentic solutions and consulting services
- Data architecture and engineering services
- Custom AI/Data software development
- SaaS products deployed to client environments (AWS, GCP, Azure)
Products:
| Product | Description | Status |
|---|---|---|
| Allama | Open-source AI security automation (SOAR) | Live |
| DBLOCK | AI workflow automation for data processing | Development |
Part 1: Strategic Vision
The 2-Year Vision (February 2026 → February 2028)
Where We Want to Be in 2 Years:
| Dimension | Current State | 2-Year Target |
|---|---|---|
| Revenue | £0 | £1.5M ARR |
| Team | Founders only | 12-15 people |
| Allama Users | Early adopters | 10,000+ MAU |
| Enterprise Customers | 0 | 25-30 |
| GitHub Stars | ~100 | 10,000+ |
| Funding | Bootstrapped | Seed round closed |
| Brand Recognition | Unknown | Known in security automation space |
Strategic Pillars:
- Product-Led Growth — Allama as the primary acquisition engine
- Services Revenue — Consulting to fund product development
- Community Building — Developer community as competitive moat
- Enterprise Sales — High-value contracts for sustainable growth
Phase Breakdown
Phase 1: Foundation (Months 1-6)
Theme: "Build the Engine"
Goals:
- Establish digital presence and brand identity
- Launch Allama 1.0 with enterprise features
- Generate first £50K in services revenue
- Build community to 500+ members
- Reach 2,000 GitHub stars
Key Milestones:
| Month | Milestone |
|---|---|
| Month 1 | Website redesign live, Discord community launched |
| Month 2 | First 3 blog posts published, LinkedIn presence established |
| Month 3 | Allama 1.0 released, Product Hunt launch |
| Month 4 | First enterprise pilot customer |
| Month 5 | First consulting contract signed (£15K+) |
| Month 6 | 500 Discord members, 2,000 GitHub stars |
Revenue Target: £50K (primarily services)
Phase 2: Traction (Months 7-12)
Theme: "Prove the Model"
Goals:
- Achieve product-market fit signals
- Close 5 enterprise customers
- Generate £150K total revenue
- Prepare for seed fundraising
- Establish thought leadership
Key Milestones:
| Month | Milestone |
|---|---|
| Month 7 | First paying Allama enterprise customer |
| Month 8 | Case study published, conference speaking slot |
| Month 9 | 5,000 GitHub stars, 1,000 Discord members |
| Month 10 | £100K ARR milestone |
| Month 11 | Seed deck finalised, investor outreach begins |
| Month 12 | 5 enterprise customers, seed term sheet |
Revenue Target: £150K cumulative (£50K products, £100K services)
Phase 3: Scale (Months 13-24)
Theme: "Accelerate Growth"
Goals:
- Close seed round (£500K-£1M)
- Scale to 25 enterprise customers
- Hire core team (engineering, sales, marketing)
- Launch DBLOCK beta
- Achieve £1.5M ARR run rate
Key Milestones:
| Month | Milestone |
|---|---|
| Month 13-14 | Seed round closed |
| Month 15 | First 3 hires (2 engineers, 1 sales) |
| Month 16 | 10 enterprise customers |
| Month 18 | DBLOCK beta launch |
| Month 20 | 15 enterprise customers, £500K ARR |
| Month 24 | 25 customers, £1.5M ARR, Series A preparation |
Revenue Target: £1.5M ARR by end of Year 2
Part 2: Business Model & Commercialisation
Open-Core Model for Allama
Following successful companies (GitLab, HashiCorp, Elastic):
| Tier | Features | Price | Target |
|---|---|---|---|
| Community | Full SOAR, 80+ integrations, AI agents, case management | Free | Practitioners, evaluation |
| Enterprise | SSO/SAML, RBAC, priority support, SLA, audit logs | £500/month | Mid-market |
| Enterprise Plus | Custom integrations, dedicated support, on-prem | £2,000/month | Large enterprise |
| Managed Cloud | Fully hosted, auto-scaling, compliance certs | Usage-based | Zero-ops teams |
Revenue Streams
| Stream | Year 1 Target | Year 2 Target |
|---|---|---|
| Enterprise Licenses | £30K | £400K |
| Managed Cloud | £0 | £200K |
| Professional Services | £20K | £150K |
| Consulting (DigitransLab) | £100K | £750K |
| Total | £150K | £1.5M |
Target Customer Segments
Primary (Year 1):
- Mid-Market SOC Teams (50-500 employees) — Need automation, budget-conscious
- MSSPs — Multi-tenant, white-label, scalable
- Cloud-Native Startups — Self-hosted, developer-friendly
Secondary (Year 2): 4. Enterprise Security (500+ employees) — Compliance, SSO, support SLAs 5. Government/Public Sector — On-prem, data sovereignty
Part 3: DigitransLab Website Strategy
Unified Website Architecture
One website serving: credibility, services, products, leads, investors, talent.
digitranslab.com/
├── / (Homepage)
├── /services/
│ ├── /ai-consulting
│ ├── /data-engineering
│ ├── /cloud-solutions
│ └── /custom-development
├── /products/
│ ├── /allama
│ └── /dblock
├── /solutions/ (by industry)
│ ├── /financial-services
│ ├── /healthcare
│ └── /technology
├── /university/ (Learning Hub)
│ ├── /tutorials — Video tutorials and guides
│ ├── /live-demos — Recorded live demos
│ ├── /tech-talks — AI & Data discussions
│ └── /webinars — Upcoming and past webinars
├── /resources/
│ ├── /blog
│ ├── /case-studies
│ └── /documentation
├── /company/
│ ├── /about
│ ├── /team
│ ├── /careers
│ └── /investors
└── /contact
University Section (Learning Hub)
Purpose: Build audience through educational content, establish thought leadership, and create a pipeline of engaged users who become customers.
Content Categories:
- Tutorials — Step-by-step video guides for Allama, DBLOCK, and general AI/Data topics
- Live Demos — Recorded product demonstrations and use case walkthroughs
- Tech Talks — Discussions on AI trends, data architecture, security automation
- Webinars — Live sessions with Q&A, guest speakers, community events
YouTube Channel Strategy:
- Channel name: DigitransLab
- Posting frequency: 2 videos/week minimum
- Video types: Tutorials (60%), Tech Talks (25%), Product Updates (15%)
- Playlists: Allama Tutorials, Data Engineering, AI Agents, Live Demos
Homepage Sections
- Hero — "AI & Data Solutions That Transform Business"
- Three Pillars — Consulting | Engineering | Products
- Products Showcase — Allama + DBLOCK cards
- Industries — Financial, Healthcare, Technology, Retail
- Why DigitransLab — Differentiators with proof points
- Testimonials — Client quotes (placeholder initially)
- CTA — "Schedule Consultation" + "Explore Products"
Part 4: Phased Implementation Roadmap
Phase 1: Foundation (Months 1-6) — Detailed Breakdown
Month 1: Digital Foundation
Focus: Establish online presence and infrastructure
| Week | Priority Tasks |
|---|---|
| Week 1 | Website redesign kickoff, domain/hosting setup |
| Week 2 | Homepage and core pages live |
| Week 3 | Discord community launched, GitHub optimised |
| Week 4 | Analytics setup, lead capture forms |
Deliverables:
- New website live at digitranslab.com
- Discord server with 50+ members
- GitHub repo optimised (README, topics, templates)
- Analytics tracking all key pages
Month 2: Content Engine
Focus: Start content marketing machine
| Week | Priority Tasks |
|---|---|
| Week 1 | Blog infrastructure, editorial calendar |
| Week 2 | First blog post: "Introducing Allama" |
| Week 3 | LinkedIn company page optimised, posting begins |
| Week 4 | Second blog post: tutorial content |
Deliverables:
- 2 blog posts published
- LinkedIn posting 3x/week
- Email newsletter setup
- 100+ LinkedIn followers
Month 3: Product Launch
Focus: Allama 1.0 public launch
| Week | Priority Tasks |
|---|---|
| Week 1 | Allama 1.0 feature freeze, documentation complete |
| Week 2 | Product Hunt launch preparation |
| Week 3 | Product Hunt launch day |
| Week 4 | Post-launch content, community engagement |
Deliverables:
- Allama 1.0 released
- Product Hunt launch (target: top 10)
- 500+ GitHub stars
- 10+ media mentions
Month 4: Enterprise Readiness
Focus: Prepare for enterprise sales
| Week | Priority Tasks |
|---|---|
| Week 1 | Enterprise features (SSO, RBAC) complete |
| Week 2 | Sales collateral created |
| Week 3 | First enterprise outreach campaign |
| Week 4 | First pilot customer onboarded |
Deliverables:
- Enterprise tier launched
- Sales deck, one-pager ready
- 5 enterprise demos booked
- 1 pilot customer
Month 5: Revenue Generation
Focus: Close first deals
| Week | Priority Tasks |
|---|---|
| Week 1 | Consulting service packages defined |
| Week 2 | Outbound to consulting prospects |
| Week 3 | First consulting proposal sent |
| Week 4 | First contract signed |
Deliverables:
- First consulting contract (£15K+)
- 2 enterprise pilots active
- Partner programme launched
- 1,000 GitHub stars
Month 6: Foundation Complete
Focus: Consolidate and prepare for scale
| Week | Priority Tasks |
|---|---|
| Week 1 | Q1 review, metrics analysis |
| Week 2 | Process documentation |
| Week 3 | Hiring plan for Phase 2 |
| Week 4 | Investor materials preparation |
Deliverables:
- £50K revenue achieved
- 500 Discord members
- 2,000 GitHub stars
- Seed deck draft ready
Part 5: Jira Implementation Tickets
Priority Legend
- P0 — Critical, blocks other work (Week 1-2)
- P1 — High priority, essential for phase goals (Week 2-4)
- P2 — Medium priority, important but not blocking (Month 2-3)
- P3 — Lower priority, nice to have (Month 4-6)
EPIC 1: Digital Foundation (Month 1)
MKTG-001: Website Information Architecture & Design
Priority: P0 | Sprint: Week 1 | Estimate: 3 days
Description: Design the complete information architecture and visual design for digitranslab.com following the unified website strategy.
AI Implementation Prompt:
Create a comprehensive website specification for digitranslab.com:
PART 1: INFORMATION ARCHITECTURE
Create a detailed sitemap with:
1. Homepage showcasing consulting services AND software products
2. Services section: AI Consulting, Data Engineering, Cloud Solutions, Custom Development
3. Products section: Allama (live), DBLOCK (coming soon)
4. Solutions by industry: Financial Services, Healthcare, Technology
5. Resources: Blog, Case Studies, Documentation links
6. Company: About, Team, Careers, Investors
7. Contact with consultation booking
For each page specify:
- URL slug
- Primary purpose
- Key content sections
- Primary and secondary CTAs
- Internal linking strategy
PART 2: HOMEPAGE WIREFRAME
Design 7 sections:
1. Hero: Headline, subheadline, 2 CTAs, trust badges
2. What We Do: 3 pillars (Consulting, Engineering, Products)
3. Products: Allama and DBLOCK cards with CTAs
4. Industries: 5 verticals with icons
5. Why DigitransLab: 5 differentiators
6. Testimonials: Placeholder format
7. Final CTA: Consultation booking
PART 3: DESIGN SYSTEM
Define:
- Colour palette (primary, secondary, accent)
- Typography (headings, body, code)
- Button styles
- Card components
- Spacing system
Use British English. Professional, modern, trustworthy aesthetic.
Acceptance Criteria:
- Complete sitemap documented
- Homepage wireframe approved
- Design system defined
- Mobile responsive considerations included
Depends On: None Blocks: MKTG-002, MKTG-003
MKTG-002: Homepage Development & Copy
Priority: P0 | Sprint: Week 2 | Estimate: 4 days
Description: Develop the homepage with all sections and compelling copy.
AI Implementation Prompt:
Write complete homepage copy for digitranslab.com:
SECTION 1: HERO
- Headline (max 8 words): Capture AI + Data + Consulting + Products
- Subheadline (max 25 words): Value proposition
- CTA 1: "Explore Services" → /services
- CTA 2: "View Products" → /products
- Trust indicators: AWS Partner | GCP Partner | Azure Partner
SECTION 2: WHAT WE DO (3 Pillars)
For each pillar provide:
- Icon suggestion
- Title (2-3 words)
- Description (20 words)
- 4 bullet points
- CTA text and destination
Pillar 1: CONSULTING - Strategic AI & Data Advisory
Pillar 2: ENGINEERING - Build & Deploy at Scale
Pillar 3: PRODUCTS - Ready-to-Deploy Solutions
SECTION 3: PRODUCTS SHOWCASE
For Allama:
- Headline: "Open-Source AI Security Automation"
- 4 key benefits (one line each)
- CTA: "Learn More" | "Try Free"
For DBLOCK:
- Headline: "AI-Powered Data Workflow Automation"
- 4 key benefits (one line each)
- CTA: "Learn More" | "Join Waitlist"
SECTION 4: INDUSTRIES (5 cards)
For each: Icon, Title, One-line description
- Financial Services
- Healthcare
- Retail & E-commerce
- Technology
- Manufacturing
SECTION 5: WHY DIGITRANSLAB
5 differentiators with supporting proof points:
- Experience (years, projects)
- Scale (events processed)
- Philosophy (open-source first)
- Flexibility (cloud-agnostic)
- Speed (POC to production timeline)
SECTION 6: TESTIMONIALS
2 placeholder formats for future testimonials
SECTION 7: FINAL CTA
- Headline
- Subheadline
- CTA 1: "Schedule Consultation"
- CTA 2: "Explore Products"
Use British English. Professional but approachable. Focus on outcomes.
Acceptance Criteria:
- All 7 sections implemented
- Copy reviewed and approved
- CTAs functional
- Mobile responsive
- Page speed < 3 seconds
Depends On: MKTG-001 Blocks: MKTG-004, MKTG-005
MKTG-003: Discord Community Expansion
Priority: P1 | Sprint: Week 3 | Estimate: 1 day
Description: Expand existing DigitransLab Discord server (with #allama-techtalks channel) to support full community engagement.
Current State:
- Server: DigitransLab (exists)
- Channel: #allama-techtalks (exists)
AI Implementation Prompt:
Expand the existing DigitransLab Discord server for full community support:
1. ADDITIONAL CHANNELS TO CREATE
Under existing structure, add:
📢 ANNOUNCEMENTS
- #welcome (read-only) — rules and links
- #announcements (read-only) — product updates
- #releases (read-only) — version releases
💬 ALLAMA COMMUNITY
- #allama-techtalks (exists) — keep as main discussion
- #allama-help — support questions
- #allama-showcase — user projects and workflows
- #allama-integrations — integration-specific help
- #allama-feature-requests — feature suggestions
👨💻 DEVELOPMENT
- #contributors — for code contributors
- #pull-requests — GitHub PR notifications
🏢 ENTERPRISE (private)
- #enterprise-support — paying customers only
📊 DBLOCK (for future)
- #dblock-announcements — when ready
2. ROLES TO CREATE
- Admin (full permissions)
- Maintainer (moderate, pin messages)
- Contributor (GitHub contributors badge)
- Enterprise (paying customers)
- Allama User (default for Allama community)
- Member (default)
3. WELCOME MESSAGE FOR #welcome
Write complete message:
- What is DigitransLab (1 sentence)
- What is Allama (2 sentences)
- Community guidelines (5 rules)
- How to get help
- Important links (GitHub, Docs, Website)
- How to contribute
4. BOT SETUP
- Auto-role assignment on join
- Welcome DM template
- GitHub integration for PR notifications to #pull-requests
5. COMMUNITY GUIDELINES
- Be respectful and professional
- No spam or excessive self-promotion
- Search before asking questions
- Use appropriate channels
- English in public channels
Acceptance Criteria:
- Additional channels created
- Roles configured with permissions
- Welcome message posted in #welcome
- Permanent invite link created
- GitHub bot integration configured
Depends On: None Blocks: MKTG-010
MKTG-004: GitHub Repository Optimisation
Priority: P0 | Sprint: Week 3 | Estimate: 2 days
Description: Optimise GitHub repository for discoverability and conversion.
AI Implementation Prompt:
Optimise the Allama GitHub repository for maximum visibility:
1. README AUDIT
Ensure README has:
- Logo and tagline at top
- Badges: Stars, License, Discord, CI status
- Product screenshot or GIF (critical!)
- Quick start (under 5 commands)
- Feature highlights (bullet list)
- Integration list
- Documentation links
- Contributing section
- License
2. REPOSITORY SETTINGS
- Description: "Open-source AI security automation platform. Automate threat detection and response with AI-powered workflows."
- Topics: security, automation, soar, siem, cybersecurity, python, ai, llm, open-source, workflow, fastapi, temporal
- Website: https://digitranslab.com/products/allama
- Social preview image (1280x640px)
3. GITHUB DISCUSSIONS
Enable and create categories:
- Announcements (maintainers only)
- Q&A (community support)
- Ideas (feature requests)
- Show and Tell (user projects)
- General
Create pinned welcome post
4. ISSUE TEMPLATES
Create templates for:
- Bug Report (environment, steps, expected, actual)
- Feature Request (problem, solution, alternatives)
- Integration Request (tool name, use case, API docs)
5. PULL REQUEST TEMPLATE
- Description
- Type of change
- Checklist (tests, docs, lint)
6. CONTRIBUTING.md
- Development setup
- Code style (Ruff, TypeScript)
- PR process
- Recognition programme
Acceptance Criteria:
- README updated with all elements
- Topics and description optimised
- Discussions enabled with categories
- Issue templates created
- Contributing guide complete
Depends On: None Blocks: MKTG-011
MKTG-005: Analytics & Tracking Setup
Priority: P1 | Sprint: Week 4 | Estimate: 1 day
Description: Set up marketing analytics infrastructure.
AI Implementation Prompt:
Set up comprehensive analytics for DigitransLab:
1. WEBSITE ANALYTICS (Plausible recommended)
- Install tracking script
- Configure goals:
- Demo request form submission
- Contact form submission
- GitHub link clicks
- Documentation visits
- Set up UTM parameter tracking
2. CONVERSION FUNNELS
Define funnels:
- Homepage → Products → GitHub → Star
- Homepage → Services → Contact → Lead
- Blog → Products → Demo Request
3. GITHUB TRACKING
Monitor:
- Star history (use star-history.com)
- Traffic sources
- Clone statistics
- Referral sources
4. SOCIAL TRACKING
- LinkedIn page analytics
- Discord server stats (member growth, activity)
5. WEEKLY DASHBOARD
Create dashboard showing:
- Website visitors (total, unique)
- Top pages
- Conversion rates
- GitHub stars (weekly change)
- Discord members (weekly change)
- Leads generated
6. UTM STRATEGY
Define UTM conventions:
- utm_source: linkedin, twitter, github, discord, email
- utm_medium: social, organic, paid, referral
- utm_campaign: [campaign-name]
Acceptance Criteria:
- Plausible/GA installed
- Goals configured
- Dashboard created
- UTM conventions documented
- Weekly reporting scheduled
Depends On: MKTG-002 Blocks: None
MKTG-005B: University Section & YouTube Channel Setup
Priority: P1 | Sprint: Week 4 | Estimate: 3 days
Description: Create the DigitransLab University learning hub on the website and establish the YouTube channel as a primary content distribution platform.
AI Implementation Prompt:
Set up DigitransLab University and YouTube channel:
1. WEBSITE UNIVERSITY SECTION
Create pages at digitranslab.com/university/:
/university (Landing Page):
- Hero: "DigitransLab University — Learn AI & Data Engineering"
- Value proposition: Free tutorials, live demos, tech talks
- Featured content carousel
- Category navigation
- Newsletter signup for new content alerts
/university/tutorials:
- Video tutorial library
- Filter by: Product (Allama, DBLOCK), Topic, Difficulty
- Each tutorial card: Thumbnail, title, duration, difficulty badge
- Embedded YouTube player
/university/live-demos:
- Recorded product demonstrations
- Use case walkthroughs
- Filter by product and industry
/university/tech-talks:
- AI & Data discussions
- Industry trends
- Guest speaker sessions
- Links to #allama-techtalks Discord channel
/university/webinars:
- Upcoming webinars with registration
- Past webinar recordings
- Calendar integration
2. YOUTUBE CHANNEL SETUP
Channel name: DigitransLab
Handle: @digitranslab
Channel branding:
- Profile picture: Purple octopus logo
- Banner: "AI & Data Solutions | Tutorials | Tech Talks"
- Channel description (write complete 500 chars)
- Links: Website, GitHub, Discord, LinkedIn
Default playlists to create:
- Allama Tutorials (getting started, workflows, integrations)
- Data Engineering (architecture, pipelines, best practices)
- AI Agents (building, deploying, monitoring)
- Live Demos (product walkthroughs)
- Tech Talks (discussions, interviews)
- Product Updates (release announcements)
3. CONTENT CALENDAR (First Month)
Week 1:
- Video 1: "Welcome to DigitransLab University" (intro, 3 min)
- Video 2: "Allama Quick Start in 5 Minutes" (tutorial, 5 min)
Week 2:
- Video 3: "Building Your First Security Workflow" (tutorial, 15 min)
- Video 4: "Why We Built Allama Open Source" (tech talk, 10 min)
Week 3:
- Video 5: "Allama + VirusTotal Integration" (tutorial, 12 min)
- Video 6: "AI Agents in Security Operations" (tech talk, 15 min)
Week 4:
- Video 7: "Live Demo: Phishing Analysis Automation" (demo, 20 min)
- Video 8: "Data Architecture Best Practices" (tech talk, 15 min)
4. VIDEO PRODUCTION STANDARDS
- Intro: 5-second branded intro
- Resolution: 1080p minimum
- Audio: Clear, no background noise
- Thumbnails: Consistent style, readable text
- End screen: Subscribe CTA, related videos
- Description template: Summary, timestamps, links
5. YOUTUBE SEO
For each video:
- Title: Include primary keyword
- Description: 200+ words with keywords
- Tags: 10-15 relevant tags
- Chapters: Timestamp markers
- Cards: Link to related content
- End screens: Subscribe + next video
6. CROSS-PROMOTION STRATEGY
- Embed videos on website University pages
- Share new videos in Discord #allama-techtalks
- LinkedIn posts for each video
- Blog posts linking to tutorials
- Email newsletter featuring new content
Acceptance Criteria:
- University landing page live
- All 4 sub-pages created (tutorials, live-demos, tech-talks, webinars)
- YouTube channel created and branded
- 6 playlists created
- First 2 videos published
- Cross-promotion workflow documented
Depends On: MKTG-002 Blocks: MKTG-006
EPIC 2: Content Marketing (Month 2)
MKTG-006: Blog Infrastructure & Editorial Calendar
Priority: P1 | Sprint: Month 2, Week 1 | Estimate: 2 days
Description: Set up blog infrastructure and create 3-month editorial calendar.
AI Implementation Prompt:
Create a 12-week blog editorial calendar for DigitransLab:
CONTENT PILLARS (distribution):
1. Security Automation (40%) — Allama-focused
2. AI & Data Engineering (30%) — Consulting expertise
3. Industry Insights (20%) — Thought leadership
4. Company Updates (10%) — Product news, culture
MONTH 1 POSTS:
Week 1: "Introducing Allama: Open-Source AI Security Automation" (launch post)
Week 2: "How to Automate Phishing Email Analysis in 30 Minutes" (tutorial)
Week 3: "The True Cost of Manual Alert Triage" (thought leadership)
Week 4: "Building Your First Security Workflow with Allama" (tutorial)
MONTH 2 POSTS:
Week 5: "Allama vs Splunk SOAR: An Honest Comparison" (comparison)
Week 6: "5 Security Workflows Every SOC Should Automate" (listicle)
Week 7: "Why We Made Allama Open Source" (company story)
Week 8: "Integrating Allama with Your SIEM" (tutorial)
MONTH 3 POSTS:
Week 9: "AI Agents in Security Operations: A Practical Guide" (thought leadership)
Week 10: "Case Study: How [Company] Reduced Alert Fatigue by 90%" (case study)
Week 11: "The Future of SOAR: AI-Native vs Legacy Platforms" (thought leadership)
Week 12: "Getting Started with Allama Enterprise" (product)
For each post specify:
- Title (SEO-optimised)
- Target keyword
- Word count target
- Target persona
- CTA at end
- Internal links to include
Acceptance Criteria:
- 12 blog topics defined with keywords
- Publishing schedule set
- Author assignments made
- SEO strategy documented
Depends On: MKTG-002 Blocks: MKTG-007
MKTG-007: Launch Blog Post — "Introducing Allama"
Priority: P1 | Sprint: Month 2, Week 2 | Estimate: 1 day
Description: Write and publish the launch announcement blog post.
AI Implementation Prompt:
Write the complete blog post "Introducing Allama: Open-Source AI Security Automation"
STRUCTURE:
1. HOOK (100 words)
- Start with the problem: SOC teams drowning in alerts
- Statistic: 500+ alerts/day, 80% false positives
2. THE PROBLEM (300 words)
- Alert fatigue is real
- Legacy SOAR tools are expensive ($100K+)
- Require consultants to implement
- Vendor lock-in
3. INTRODUCING ALLAMA (400 words)
- What it is (one paragraph)
- Why we built it (founder story)
- Key differentiators:
- 100% open source
- AI-native (not bolted on)
- Self-hosted (data sovereignty)
- Developer-friendly
4. KEY FEATURES (400 words)
- Visual workflow builder
- AI agents for triage
- 80+ integrations
- Case management
- Secure script execution
Include screenshot placeholders
5. GETTING STARTED (200 words)
- Quick start commands
- Link to documentation
- Link to GitHub
6. WHAT'S NEXT (150 words)
- Roadmap teaser
- Enterprise features coming
- Community growth plans
7. CALL TO ACTION (100 words)
- Star on GitHub
- Join Discord
- Try it today
TOTAL: ~1,650 words
TONE: Excited but professional. Technical credibility. British English.
KEYWORDS: open source SOAR, security automation, AI security, threat response
Acceptance Criteria:
- Post written and edited
- Screenshots/images added
- SEO metadata complete
- Published and promoted
Depends On: MKTG-006 Blocks: None
MKTG-008: Tutorial — "Automate Phishing Analysis"
Priority: P1 | Sprint: Month 2, Week 3 | Estimate: 2 days
Description: Write comprehensive tutorial showing Allama's value.
AI Implementation Prompt:
Write a complete tutorial: "How to Automate Phishing Email Analysis with Allama"
TARGET: Security engineers, SOC analysts
LENGTH: 2,500 words with code examples
STRUCTURE:
1. INTRODUCTION (200 words)
- The problem: manual phishing analysis takes 15-30 minutes per email
- The solution: automate to 30 seconds
- What you'll build
2. PREREQUISITES (100 words)
- Allama installed
- API keys for: VirusTotal, URLScan
- Email ingestion configured
3. ARCHITECTURE OVERVIEW (200 words)
- Diagram of the workflow
- Components involved
- Data flow explanation
4. STEP 1: CREATE THE WORKFLOW (400 words)
- Navigate to Workflows
- Create new workflow
- Configure webhook trigger
- Include screenshots
5. STEP 2: EXTRACT INDICATORS (400 words)
- Add extraction action
- Parse URLs, attachments, sender
- Handle edge cases
- Include YAML snippet
6. STEP 3: THREAT INTELLIGENCE LOOKUP (400 words)
- Add VirusTotal action
- Add URLScan action
- Parallel execution
- Include YAML snippet
7. STEP 4: AI CLASSIFICATION (300 words)
- Add AI agent action
- Configure prompt for classification
- Severity scoring
- Include YAML snippet
8. STEP 5: RESPONSE ACTIONS (300 words)
- Create case if malicious
- Notify analyst
- Block sender (optional)
- Include YAML snippet
9. TESTING & RESULTS (200 words)
- How to test the workflow
- Expected results
- Metrics to track
10. CONCLUSION (100 words)
- Summary of what was built
- Time savings achieved
- Next steps
Include complete workflow YAML at the end.
Acceptance Criteria:
- Tutorial complete with all steps
- Code examples tested and working
- Screenshots added
- Published and promoted
Depends On: MKTG-007 Blocks: None
MKTG-009: LinkedIn Content Strategy
Priority: P1 | Sprint: Month 2, Week 1 | Estimate: 1 day
Description: Create LinkedIn content calendar and first month of posts.
AI Implementation Prompt:
Create LinkedIn content strategy for DigitransLab:
POSTING SCHEDULE: 5 posts per week (Mon-Fri)
CONTENT MIX:
- Monday: Industry insight / thought leadership
- Tuesday: Product tip / feature highlight
- Wednesday: Technical content / tutorial teaser
- Thursday: Company culture / team spotlight
- Friday: Community engagement / question
WEEK 1 POSTS (write complete):
POST 1 (Monday) - Launch Announcement:
"We just open-sourced Allama — an AI-powered security automation platform.
After months of building, it's finally live on GitHub.
What it does:
• Automates alert triage with LLMs
• Builds workflows with drag-and-drop
• Integrates with 80+ security tools
• Self-hosted (your data stays yours)
Why open source?
Security tools should be transparent. You should be able to see exactly what's running in your environment.
Link in comments 👇
#OpenSource #Cybersecurity #SecurityAutomation"
POST 2 (Tuesday) - Problem Statement:
[Write complete post about alert fatigue]
POST 3 (Wednesday) - Technical Tip:
[Write complete post about a specific Allama feature]
POST 4 (Thursday) - Company Story:
[Write complete post about why we built Allama]
POST 5 (Friday) - Engagement:
[Write complete post with question for audience]
HASHTAG STRATEGY:
Primary: #SecurityAutomation #OpenSource #Cybersecurity
Secondary: #SOAR #SOC #InfoSec #AI #LLM
Limit: 5-7 hashtags per post
ENGAGEMENT RULES:
- Respond to all comments within 4 hours
- Like and comment on 5 relevant posts daily
- Connect with commenters
Acceptance Criteria:
- 20 posts written (4 weeks)
- Hashtag strategy defined
- Posting schedule set
- Engagement process documented
Depends On: MKTG-002 Blocks: None
EPIC 3: Product Launch (Month 3)
MKTG-010: Product Hunt Launch Preparation
Priority: P1 | Sprint: Month 3, Week 1-2 | Estimate: 5 days
Description: Prepare all assets and strategy for Product Hunt launch.
AI Implementation Prompt:
Create complete Product Hunt launch plan for Allama:
1. LAUNCH ASSETS
Thumbnail (240x240px):
- Purple octopus logo on clean background
- No text (won't be readable at small size)
Gallery Images (1270x760px, 8 images):
Image 1: Hero shot - main dashboard with headline overlay
Image 2: Workflow builder in action
Image 3: AI agent configuration
Image 4: Integration ecosystem (logo grid)
Image 5: Case management view
Image 6: Before/after metrics comparison
Image 7: Enterprise features highlight
Image 8: Community/GitHub stats
Video (optional, 60-90 seconds):
- Screen recording of building a workflow
- No talking head, just product + music
- Show: create workflow → add actions → run → see results
2. COPY
Tagline (60 chars max):
"Open-source AI security automation for modern SOC teams"
Description (260 chars max):
"Allama helps security teams automate threat detection and response with AI-powered workflows. Self-hosted or cloud. 80+ integrations. Visual workflow builder. Free and open source."
Maker Comment (first comment after launch):
[Write complete 300-word maker comment explaining:
- Who you are
- Why you built it
- Key features
- What feedback you want
- Links to GitHub and docs]
3. LAUNCH STRATEGY
Timing:
- Launch at 12:01 AM Pacific Time
- Best days: Tuesday, Wednesday, Thursday
- Avoid major tech news days
Pre-launch (2 weeks before):
- Build Product Hunt following
- Engage with other launches
- Notify community of upcoming launch
Launch day schedule:
- 12:01 AM: Product goes live
- 12:05 AM: Post maker comment
- 6:00 AM: Email newsletter blast
- 9:00 AM: LinkedIn/Twitter posts
- Throughout day: Respond to ALL comments
- 6:00 PM: Thank you post
Post-launch:
- Blog post: "What We Learned Launching on Product Hunt"
- Add PH badge to website
- Follow up with commenters
4. OUTREACH LIST
- 50 people to personally notify
- Discord community announcement
- Twitter/LinkedIn posts
- Email to newsletter subscribers
- Slack communities to share in
Acceptance Criteria:
- All gallery images created
- Video produced (optional)
- Copy written and reviewed
- Launch day schedule documented
- Outreach list prepared
Depends On: MKTG-004 Blocks: MKTG-011
MKTG-011: Product Hunt Launch Execution
Priority: P0 | Sprint: Month 3, Week 3 | Estimate: 1 day
Description: Execute Product Hunt launch and manage launch day activities.
AI Implementation Prompt:
Execute Product Hunt launch for Allama:
LAUNCH DAY CHECKLIST:
PRE-LAUNCH (Night Before):
- [ ] Verify all assets uploaded
- [ ] Schedule launch for 12:01 AM PT
- [ ] Prepare maker comment in notes
- [ ] Set alarms for key times
- [ ] Notify team of responsibilities
LAUNCH (12:01 AM PT):
- [ ] Confirm product is live
- [ ] Post maker comment immediately
- [ ] Share link in Discord
- [ ] Tweet announcement
- [ ] Post on LinkedIn
MORNING (6:00 AM PT):
- [ ] Send email to newsletter
- [ ] Check and respond to all comments
- [ ] Share in relevant Slack communities
- [ ] Update team on progress
MIDDAY (12:00 PM PT):
- [ ] Post update on social media
- [ ] Continue responding to comments
- [ ] Thank early supporters publicly
- [ ] Check ranking and adjust strategy
EVENING (6:00 PM PT):
- [ ] Final comment responses
- [ ] Thank you post on social media
- [ ] Document lessons learned
- [ ] Plan follow-up content
POST-LAUNCH METRICS TO TRACK:
- Final ranking
- Total upvotes
- Comments received
- GitHub stars gained
- Website traffic spike
- New Discord members
- Demo requests
RESPONSE TEMPLATES:
For positive comments: [template]
For questions: [template]
For feature requests: [template]
For criticism: [template]
Acceptance Criteria:
- Launch executed on schedule
- All comments responded to
- Metrics documented
- Lessons learned captured
Depends On: MKTG-010 Blocks: None
MKTG-012: Post-Launch Content
Priority: P2 | Sprint: Month 3, Week 4 | Estimate: 2 days
Description: Create content capitalising on Product Hunt launch momentum.
AI Implementation Prompt:
Create post-Product Hunt launch content:
1. BLOG POST: "What We Learned Launching Allama on Product Hunt"
Structure:
- Our results (transparent about ranking, upvotes)
- What worked well
- What we'd do differently
- Community feedback themes
- What's next for Allama
Length: 1,500 words
2. LINKEDIN POST: Launch Results
- Share results transparently
- Thank the community
- Highlight interesting feedback
- Announce next steps
3. TWITTER THREAD: Launch Retrospective
- 10-tweet thread
- Behind the scenes of launch prep
- Key learnings
- Metrics achieved
- Thank supporters
4. EMAIL TO SUBSCRIBERS: Launch Update
- Thank them for support
- Share results
- Highlight new features coming
- Ask for feedback
5. DISCORD ANNOUNCEMENT: Thank You
- Thank community for support
- Share results
- Celebrate together
- Outline roadmap
Acceptance Criteria:
- Blog post published
- Social posts scheduled
- Email sent
- Discord announcement posted
Depends On: MKTG-011 Blocks: None
EPIC 4: Enterprise Sales (Month 4-5)
MKTG-013: Enterprise Features Launch
Priority: P1 | Sprint: Month 4, Week 1 | Estimate: 3 days
Description: Launch enterprise tier with SSO, RBAC, and support SLAs.
AI Implementation Prompt:
Create enterprise tier launch materials:
1. ENTERPRISE FEATURES PAGE
URL: digitranslab.com/products/allama/enterprise
Sections:
- Hero: "Allama Enterprise: Security Automation at Scale"
- Feature comparison table (Community vs Enterprise)
- Security & Compliance section
- Support SLA details
- Pricing (contact sales)
- Demo booking CTA
Features to highlight:
- SSO/SAML (Okta, Azure AD, Google)
- Advanced RBAC
- Audit logging
- Priority support (4-hour SLA)
- Custom integrations
- Dedicated success manager
- On-premises deployment option
2. ENTERPRISE DATASHEET (PDF)
- 2-page PDF
- Feature overview
- Security certifications
- Deployment options
- Support tiers
- Contact information
3. SECURITY WHITEPAPER
- Architecture overview
- Data handling
- Encryption (at rest, in transit)
- Authentication methods
- Compliance (SOC2, GDPR readiness)
- Penetration testing results
4. ENTERPRISE DEMO SCRIPT
- 30-minute demo flow
- Key talking points
- Objection handling
- Discovery questions
- Next steps
Acceptance Criteria:
- Enterprise page live
- Datasheet created
- Security whitepaper complete
- Demo script documented
Depends On: MKTG-002 Blocks: MKTG-014
MKTG-014: Sales Collateral
Priority: P1 | Sprint: Month 4, Week 2 | Estimate: 3 days
Description: Create sales enablement materials for enterprise conversations.
AI Implementation Prompt:
Create sales collateral for Allama enterprise sales:
1. ONE-PAGER (PDF)
- Company overview
- Product summary
- Key benefits (3)
- Customer proof points
- Pricing overview
- Contact information
Design: Clean, professional, printable
2. PRODUCT DECK (10 slides)
Slide 1: Title + tagline
Slide 2: Problem statement
Slide 3: Solution overview
Slide 4: Key features
Slide 5: Architecture diagram
Slide 6: Integration ecosystem
Slide 7: Customer success story (placeholder)
Slide 8: Pricing tiers
Slide 9: Implementation timeline
Slide 10: Next steps + contact
3. ROI CALCULATOR
Spreadsheet template:
- Current state inputs (alerts/day, analysts, tools)
- Allama impact assumptions
- Time savings calculation
- Cost savings calculation
- ROI summary
4. COMPETITIVE BATTLECARDS
For each competitor (Splunk SOAR, XSOAR, Swimlane):
- Overview
- Strengths
- Weaknesses
- Our advantages
- Objection handling
- Win themes
5. SECURITY QUESTIONNAIRE
Pre-filled responses for:
- Data handling
- Authentication
- Encryption
- Compliance (SOC2, GDPR)
- Deployment options
Acceptance Criteria:
- One-pager designed
- Product deck complete
- ROI calculator functional
- Battlecards created
- Security questionnaire ready
Depends On: MKTG-013 Blocks: MKTG-015
MKTG-015: Enterprise Outreach Campaign
Priority: P1 | Sprint: Month 4, Week 3-4 | Estimate: 5 days
Description: Launch outbound campaign to enterprise security leaders.
AI Implementation Prompt:
Create enterprise outreach campaign:
1. TARGET LIST BUILDING
Criteria:
- Company size: 200-2000 employees
- Industries: Technology, Financial Services, Healthcare
- Roles: CISO, VP Security, Security Director, SOC Manager
- Signals: Hiring for security automation, SOAR evaluation
Sources:
- LinkedIn Sales Navigator
- Job postings (companies hiring SOAR roles)
- Conference attendee lists
- Competitor customer lists
Target: 200 qualified prospects
2. EMAIL SEQUENCES
Sequence 1: Cold Outreach (5 emails)
Email 1: Problem-focused intro
Email 2: Social proof / case study
Email 3: Value proposition
Email 4: Offer demo
Email 5: Break-up email
Sequence 2: Inbound Follow-up (3 emails)
Email 1: Thank you + next steps
Email 2: Additional resources
Email 3: Demo reminder
3. LINKEDIN OUTREACH
Connection request template:
"Hi [Name], I noticed you're leading security at [Company]. We're building an open-source SOAR platform and I'd love to connect with security leaders in the space."
Follow-up message template:
[After connection accepted]
4. CALL SCRIPTS
Discovery call script:
- Opening
- Discovery questions
- Pain point exploration
- Solution positioning
- Next steps
Demo call script:
- Agenda setting
- Product walkthrough
- Q&A handling
- Closing
5. TRACKING
- CRM setup (HubSpot free)
- Pipeline stages
- Activity metrics
- Conversion tracking
Acceptance Criteria:
- Target list of 200 prospects
- Email sequences written
- LinkedIn templates ready
- Call scripts documented
- CRM configured
Depends On: MKTG-014 Blocks: None
EPIC 5: Consulting Revenue (Month 5)
MKTG-016: Services Packaging
Priority: P1 | Sprint: Month 5, Week 1 | Estimate: 2 days
Description: Define and package consulting service offerings.
AI Implementation Prompt:
Create consulting service packages for DigitransLab:
1. SERVICE PACKAGES
PACKAGE 1: AI READINESS ASSESSMENT
Duration: 2 weeks
Price: £5,000
Deliverables:
- Current state analysis
- Use case identification
- Technology evaluation
- AI roadmap document
- Executive presentation
PACKAGE 2: DATA PLATFORM DESIGN
Duration: 4 weeks
Price: £15,000
Deliverables:
- Requirements gathering
- Architecture design
- Technology selection
- Implementation plan
- Cost estimation
PACKAGE 3: AI AGENT DEVELOPMENT
Duration: 6-12 weeks
Price: £25,000-£50,000
Deliverables:
- Agent design
- Development
- Integration
- Testing
- Documentation
- Training
PACKAGE 4: ALLAMA IMPLEMENTATION
Duration: 2-4 weeks
Price: £10,000-£20,000
Deliverables:
- Installation and configuration
- Integration setup
- Workflow development
- Training
- Go-live support
2. SERVICES PAGE CONTENT
For each package:
- Overview
- Who it's for
- What's included
- Timeline
- Pricing (or "Contact for quote")
- CTA
3. PROPOSAL TEMPLATES
- Cover page
- Executive summary
- Scope of work
- Timeline
- Team
- Investment
- Terms
- Signature page
4. SOW TEMPLATE
- Project overview
- Deliverables
- Timeline
- Assumptions
- Responsibilities
- Change process
- Payment terms
Acceptance Criteria:
- 4 service packages defined
- Services page content written
- Proposal template created
- SOW template ready
Depends On: MKTG-002 Blocks: MKTG-017
MKTG-017: Consulting Outreach
Priority: P1 | Sprint: Month 5, Week 2-3 | Estimate: 5 days
Description: Launch outbound campaign for consulting services.
AI Implementation Prompt:
Create consulting services outreach campaign:
1. TARGET SEGMENTS
Segment 1: AI Transformation
- Companies starting AI journey
- Hiring AI/ML roles
- Budget for consulting
Roles: CTO, VP Engineering, Head of Data
Segment 2: Data Platform Modernisation
- Legacy data infrastructure
- Cloud migration planned
- Data team scaling
Roles: VP Data, Chief Data Officer, Data Engineering Lead
Segment 3: Security Automation
- SOC teams
- SOAR evaluation
- Allama interest
Roles: CISO, Security Director, SOC Manager
2. OUTREACH CHANNELS
LinkedIn:
- Personal profile optimisation
- Content posting (thought leadership)
- Direct outreach to targets
- Group participation
Email:
- Cold outreach sequences
- Newsletter to subscribers
- Referral requests
Network:
- Former colleagues
- Industry contacts
- Conference connections
3. CONTENT FOR OUTREACH
Case study format:
- Challenge
- Solution
- Results
- Testimonial
Thought leadership topics:
- "5 Signs Your Data Platform Needs Modernisation"
- "AI Implementation: Build vs Buy"
- "The True Cost of DIY Security Automation"
4. REFERRAL PROGRAMME
- Referral incentive (10% of first contract)
- Partner agreements
- Tracking mechanism
Acceptance Criteria:
- Target list built
- Outreach sequences created
- Content calendar set
- Referral programme launched
Depends On: MKTG-016 Blocks: None
EPIC 6: Investor Preparation (Month 6)
MKTG-018: Pitch Deck Creation
Priority: P1 | Sprint: Month 6, Week 1-2 | Estimate: 5 days
Description: Create investor pitch deck for seed fundraising.
AI Implementation Prompt:
Create a 15-slide investor pitch deck for DigitransLab:
SLIDE 1: TITLE
- Company name and logo
- Tagline: "AI & Data Solutions for the Enterprise"
- Presenter name and date
SLIDE 2: PROBLEM
- Security teams overwhelmed (500+ alerts/day)
- Data teams drowning in complexity
- Legacy tools expensive and inflexible
- Include statistics
SLIDE 3: SOLUTION
- DigitransLab: Consulting + Products
- Allama: Security automation
- DBLOCK: Data workflow automation
- Visual showing the ecosystem
SLIDE 4: MARKET OPPORTUNITY
- TAM: Global AI/Data market ($XXB)
- SAM: Security automation + Data platforms
- SOM: Initial target segments
- Growth projections
SLIDE 5: PRODUCT - ALLAMA
- What it does
- Key differentiators
- Screenshot/demo
- Traction metrics
SLIDE 6: PRODUCT - DBLOCK
- What it does
- Market opportunity
- Development status
- Launch timeline
SLIDE 7: SERVICES
- Consulting offerings
- Revenue contribution
- Client examples
- Growth potential
SLIDE 8: BUSINESS MODEL
- Revenue streams
- Pricing strategy
- Unit economics
- Path to profitability
SLIDE 9: TRACTION
- GitHub stars
- Community size
- Revenue (if any)
- Pipeline value
- Key customers/logos
SLIDE 10: GO-TO-MARKET
- PLG for Allama
- Enterprise sales motion
- Partner channels
- Geographic expansion
SLIDE 11: COMPETITION
- Competitive landscape
- Positioning matrix
- Sustainable advantages
- Barriers to entry
SLIDE 12: TEAM
- Founders and key hires
- Relevant experience
- Advisory board
- Hiring plan
SLIDE 13: FINANCIALS
- Revenue projections (3 years)
- Key assumptions
- Burn rate
- Path to break-even
SLIDE 14: THE ASK
- Funding amount (£500K-£1M)
- Use of funds breakdown
- Milestones to achieve
- Timeline
SLIDE 15: CLOSING
- Vision statement
- Contact information
- Appendix reference
Acceptance Criteria:
- All 15 slides complete
- Design consistent and professional
- Data points verified
- Narrative compelling
Depends On: MKTG-014 Blocks: MKTG-019
MKTG-019: Investor One-Pager
Priority: P1 | Sprint: Month 6, Week 2 | Estimate: 1 day
Description: Create one-page investor summary for email outreach.
AI Implementation Prompt:
Create a one-page investor summary for DigitransLab:
FORMAT: Single page PDF, clean design
SECTIONS:
1. HEADER
- Logo
- Tagline
- Website URL
2. THE OPPORTUNITY (2-3 sentences)
- Market problem
- Why now
3. OUR SOLUTION (2-3 sentences)
- What we do
- Key products
4. TRACTION (bullet points)
- GitHub stars
- Community size
- Revenue/pipeline
- Key customers
5. MARKET (2-3 data points)
- TAM
- Growth rate
- Trends
6. TEAM (brief)
- Founders
- Key experience
7. THE ASK
- Funding amount
- Use of funds (3 bullets)
8. CONTACT
- Email
- Calendar link
- LinkedIn
Design guidelines:
- Professional, not flashy
- Easy to scan in 30 seconds
- Include one visual (product screenshot or market chart)
- Leave white space
Acceptance Criteria:
- One-pager complete
- Design reviewed
- All data accurate
- PDF optimised for email
Depends On: MKTG-018 Blocks: MKTG-020
MKTG-020: Investor Outreach
Priority: P2 | Sprint: Month 6, Week 3-4 | Estimate: 5 days
Description: Begin investor outreach for seed round.
AI Implementation Prompt:
Create investor outreach strategy:
1. TARGET INVESTOR LIST
Tier 1: Perfect Fit (20 investors)
- Cybersecurity-focused VCs
- Open-source focused VCs
- European seed funds
Examples: YL Ventures, Cyberstarts, OSS Capital, Heavybit
Tier 2: Good Fit (30 investors)
- Enterprise software VCs
- AI/ML focused funds
- Generalist seed funds
Tier 3: Angels (50 investors)
- Former CISOs
- Open-source founders
- Enterprise software operators
2. OUTREACH SEQUENCE
Week 1: Warm introductions
- Map network connections
- Request introductions
- Personalised outreach
Week 2: Cold outreach (Tier 1)
- Email with one-pager
- LinkedIn connection
- Follow-up sequence
Week 3: Cold outreach (Tier 2)
- Same approach
- Track responses
Week 4: Angel outreach
- Personal approach
- Smaller ask
- Advisory potential
3. EMAIL TEMPLATES
Cold email template:
Subject: Open-source security automation - DigitransLab
Hi [Name],
I'm [Founder], building DigitransLab — an AI & Data company with an open-source security automation product (Allama) that's gaining traction.
Quick stats:
- [X] GitHub stars
- [X] Discord community members
- [X] enterprise pilots
- £[X]K in consulting revenue
We're raising a £[X] seed round to accelerate product development and go-to-market.
Would you be open to a 20-minute call to share what we're building?
[Calendar link]
Best,
[Name]
4. TRACKING
- CRM for investor pipeline
- Follow-up reminders
- Meeting notes
- Term sheet tracking
Acceptance Criteria:
- Investor list of 100 targets
- Outreach sequences ready
- Tracking system set up
- First meetings scheduled
Depends On: MKTG-019 Blocks: None
EPIC 7: Phase 2 Preparation (Month 6)
MKTG-021: Partner Programme Design
Priority: P2 | Sprint: Month 6, Week 1 | Estimate: 2 days
Description: Design MSSP and technology partner programme for Phase 2.
AI Implementation Prompt:
Design the Allama Partner Programme:
1. PARTNER TYPES
- MSSP Partners (resell + manage)
- Technology Partners (integrations)
- Consulting Partners (implementation)
- Referral Partners (lead generation)
2. MSSP PROGRAMME
Benefits:
- White-label options
- Volume discounts (20-40%)
- Co-marketing funds
- Technical training
- Dedicated support
Requirements:
- 2 certified engineers
- 3 customer deployments in Year 1
- Quarterly business reviews
3. TECHNOLOGY PARTNER PROGRAMME
Benefits:
- Integration listing in marketplace
- Co-marketing opportunities
- Technical support
- Early access to features
Requirements:
- Working integration
- Documentation
- Support commitment
4. PARTNER PORTAL REQUIREMENTS
- Deal registration
- Marketing assets
- Training materials
- Support tickets
- Commission tracking
5. PARTNER AGREEMENT TEMPLATE
- Territory rights
- Pricing and margins
- Support responsibilities
- Termination clauses
Acceptance Criteria:
- Programme tiers defined
- Benefits documented
- Requirements specified
- Agreement template created
Depends On: MKTG-014 Blocks: None
MKTG-022: Conference Strategy
Priority: P3 | Sprint: Month 6, Week 2 | Estimate: 1 day
Description: Plan conference presence for Phase 2.
AI Implementation Prompt:
Create conference strategy for DigitransLab:
1. TARGET CONFERENCES (Year 1-2)
Security-focused:
- BSides London (attend, speak)
- BSides Las Vegas (attend)
- RSA Conference (attend Year 2)
- Black Hat Europe (attend Year 2)
Data/AI-focused:
- Data Council (attend)
- AI Summit London (attend, speak)
Startup-focused:
- SaaStock (attend)
- Web Summit (attend Year 2)
2. CFP SUBMISSIONS
Create 3 talk abstracts:
- "Building AI-Native Security Automation"
- "Open Source SOAR: Lessons from Allama"
- "From Alert Fatigue to AI Triage"
3. BUDGET ESTIMATES
Per conference:
- Registration: £500-£2,000
- Travel: £500-£1,500
- Accommodation: £500-£1,000
- Sponsorship: £5,000-£50,000
Year 1 budget: £15,000
Year 2 budget: £50,000
4. ROI FRAMEWORK
- Leads generated
- Partnerships formed
- Brand awareness
- Hiring pipeline
Acceptance Criteria:
- Conference calendar created
- CFP abstracts written
- Budget estimated
- ROI framework defined
Depends On: None Blocks: None
MKTG-023: Hiring Plan
Priority: P2 | Sprint: Month 6, Week 3 | Estimate: 1 day
Description: Create hiring plan for Phase 2 growth.
AI Implementation Prompt:
Create hiring plan for DigitransLab Phase 2:
1. HIRING TIMELINE
Month 13-14 (Post-Seed):
- Senior Backend Engineer (Allama)
- Frontend Engineer (Allama)
Month 15-16:
- Sales Development Rep
- DevRel / Community Manager
Month 17-18:
- Senior Backend Engineer (DBLOCK)
- Solutions Engineer
Month 19-24:
- Marketing Manager
- Customer Success Manager
- Additional engineers as needed
2. JOB DESCRIPTIONS
Senior Backend Engineer:
- Python, FastAPI, Temporal
- Security domain experience preferred
- Open-source contribution history
- Remote-first
Sales Development Rep:
- B2B SaaS experience
- Security/DevOps market knowledge
- Outbound prospecting skills
- UK-based preferred
DevRel / Community Manager:
- Developer community experience
- Content creation skills
- Public speaking
- Open-source background
3. COMPENSATION BENCHMARKS
- Engineers: £70-100K + equity
- Sales: £40-60K base + commission
- DevRel: £50-70K + equity
4. HIRING PROCESS
- Job posting (LinkedIn, AngelList, remote job boards)
- Initial screen (30 min)
- Technical/skills assessment
- Team interview
- Founder interview
- Offer
5. EMPLOYER BRANDING
- Careers page content
- Company culture document
- Benefits overview
- Team photos/bios
Acceptance Criteria:
- Hiring timeline defined
- Job descriptions written
- Compensation benchmarks set
- Hiring process documented
Depends On: MKTG-018 Blocks: None
Part 6: Daily/Weekly Marketing Tasks
Daily Tasks (30 minutes)
| Time | Task | Platform |
|---|---|---|
| 9:00 | Check and respond to GitHub issues | GitHub |
| 9:10 | Respond to Discord messages | Discord |
| 9:20 | Engage with LinkedIn posts (comment on 3-5) | |
| 9:30 | Check analytics dashboard | Plausible/GA |
Weekly Tasks
| Day | Task | Duration |
|---|---|---|
| Monday | Publish blog post | 2 hours |
| Monday | Schedule week's social posts | 1 hour |
| Tuesday | Community engagement (Reddit, HN) | 1 hour |
| Wednesday | Outreach to potential partners/customers | 2 hours |
| Thursday | Content creation (tutorials, docs) | 3 hours |
| Friday | Analytics review and planning | 1 hour |
| Friday | GitHub repository maintenance | 1 hour |
Monthly Tasks
| Task | Duration |
|---|---|
| Editorial calendar planning | 2 hours |
| Competitor analysis update | 2 hours |
| Website content audit | 2 hours |
| Email sequence optimisation | 2 hours |
| Partner programme outreach | 3 hours |
| Investor update email | 1 hour |
Part 7: Success Metrics & KPIs
Phase 1 Metrics (Months 1-6)
| Metric | Month 1 | Month 3 | Month 6 |
|---|---|---|---|
| GitHub Stars | 200 | 500 | 2,000 |
| Discord Members | 50 | 200 | 500 |
| Website Visitors | 500 | 2,000 | 5,000 |
| Blog Posts | 1 | 4 | 8 |
| LinkedIn Followers | 100 | 300 | 1,000 |
| Enterprise Leads | 0 | 5 | 20 |
| Revenue | £0 | £0 | £50K |
Phase 2 Metrics (Months 7-12)
| Metric | Month 9 | Month 12 |
|---|---|---|
| GitHub Stars | 5,000 | 7,000 |
| Discord Members | 1,000 | 1,500 |
| Website Visitors | 15,000 | 25,000 |
| Enterprise Customers | 2 | 5 |
| ARR | £50K | £100K |
| Consulting Revenue | £50K | £100K |
Phase 3 Metrics (Months 13-24)
| Metric | Month 18 | Month 24 |
|---|---|---|
| GitHub Stars | 8,000 | 10,000 |
| Discord Members | 2,500 | 5,000 |
| Enterprise Customers | 15 | 25 |
| ARR | £500K | £1.5M |
| Team Size | 8 | 15 |
Part 8: Risk Mitigation
Key Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Slow community growth | Medium | High | Increase content output, paid promotion |
| Enterprise sales cycle too long | High | Medium | Focus on mid-market, offer pilots |
| Competitor launches similar product | Medium | Medium | Differentiate on AI-native, community |
| Funding not secured | Medium | High | Bootstrap longer, focus on services revenue |
| Key hire doesn't work out | Medium | Medium | Thorough hiring process, probation period |
Contingency Plans
If GitHub stars < 1,000 by Month 6:
- Increase content marketing
- Launch referral programme
- Consider paid promotion (GitHub sponsors, etc.)
If no enterprise customers by Month 9:
- Pivot to MSSP channel
- Offer extended free pilots
- Focus on smaller companies
If seed round not closed by Month 12:
- Extend runway with consulting revenue
- Reduce burn rate
- Consider alternative funding (grants, angels)
Appendix: Resource Links
Tools Recommended
| Category | Tool | Cost |
|---|---|---|
| Website | Vercel + Next.js | Free |
| Analytics | Plausible | £9/month |
| Buttondown | Free (up to 100) | |
| CRM | HubSpot | Free tier |
| Social Scheduling | Buffer | Free tier |
| Design | Figma | Free tier |
| Video | Loom | Free tier |
Competitor Research
| Competitor | Pricing | Strengths | Weaknesses |
|---|---|---|---|
| Splunk SOAR | $100K+/year | Enterprise features, brand | Expensive, complex |
| Palo Alto XSOAR | $80K+/year | Ecosystem, support | Vendor lock-in |
| Swimlane | $50K+/year | Modern UI | Limited AI |
| Shuffle | Free | Open source | Limited features |
| Tines | $30K+/year | No-code | Not open source |
Last Updated: February 2026 Document Owner: Marketing Team Review Cadence: Monthly
What's inside
5 parts: strategic vision, business model, website architecture, phased roadmap, and 8 Jira tickets with AI prompts and acceptance criteria
Change this for your project
- Replace
DigitransLabwith your company name throughout - Replace
AllamaandDBLOCKwith your product names - Replace
digitranslab.comwith your domain - Replace revenue targets like
£1.5M ARRand£50Kwith your own figures
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Jira tickets with embedded AI prompts that generate copy, wireframes, and channel setup instructions
- A 3-tier open-core pricing model (Community, Enterprise, Enterprise Plus, Managed Cloud) with target segments
- A University/learning hub as a content distribution engine with YouTube playlist strategy and cross-promotion workflow
Related Documents
Content Calendar - Notion Template
Provides a complete Notion-based content calendar system with databases, workflows, and templates for planning, publishing, and repurposing content across multiple platforms.
Content Standards
Defines content strategy, writing guidelines, tone, and editorial workflows for multi-format content including documentation, marketing copy, and UI text.
CTO Personal Website - Comprehensive Content Strategy
This content strategy document outlines a comprehensive approach to positioning a Chief Technology Officer (CTO) as a thought leader in the technology industry through strategic content creation, professional messaging, and industry expertise showcase.
Draft Mode Product Roadmap
Lays out a four-phase product roadmap for a version control tool for writers, covering features, marketing, metrics, and team growth.