Inspiration
Creator agencies manage hundreds of creator contracts at the same time. Each contract contains critical operational logic—deadlines, posting requirements, payment conditions—but all of it is buried in unstructured text.
While Jira is excellent at tracking work, it cannot understand contracts. As a result, teams rely on spreadsheets, manual reminders, and institutional memory to bridge the gap between agreements and execution.
CreatorDeal was inspired by this disconnect: contracts already define the work, but there is no system that turns them into something Jira can actually run.
What it does
CreatorDeal is an Atlassian Forge app that transforms creator contracts into executable Jira workflows.
Users paste contract text into the app, review extracted key information, and generate a structured Jira epic with sequential tasks that represent the real operational lifecycle of a creator deal—content production, performance checks, payment processing, and account transfer.
Instead of treating contracts as static reference documents, CreatorDeal makes them the source of truth that drives planning, execution, and communication directly inside Jira.
How we built it
CreatorDeal is built entirely on Atlassian Forge using TypeScript.
The backend analyzes contract text using a dual extraction approach: deterministic pattern matching for reliability, with optional LLM-based semantic extraction (Gemini or OpenAI) for more complex language. Extracted data is normalized into a contract model that maps directly to Jira workflow structures.
The app generates Jira epics and tasks with automatic dependencies and due dates, optionally creates Confluence documentation pages, and provides pre-generated email templates inside Jira issues to streamline creator communication.
The frontend is built with React and Atlaskit, following a simple intake → preview → confirm flow to ensure users remain in control of extracted data before workflows are created.
Challenges we ran into
One major challenge was balancing automation with reliability. Fully relying on LLMs would make extraction unpredictable, while purely deterministic rules would be too rigid.
Another challenge was working within Forge’s constraints while still delivering a responsive, multi-step user experience and handling partial failures gracefully—such as when external APIs or optional integrations are unavailable.
Designing a workflow that felt natural to Jira users, rather than bolted on, was also a key consideration.
Accomplishments that I'm proud of
Turning unstructured contract text into structured, executable Jira workflows
Designing a dual extraction strategy that prioritizes reliability over novelty
Building a Forge-native app that feels integrated with Jira rather than external
Providing operationally useful task descriptions and email templates derived directly from contract logic
Implementing graceful degradation so the core workflow still works even when optional services are unavailable
What's next for Creator Deal
Next, CreatorDeal could expand to support additional contract types and more flexible workflow templates.
Future work may include deeper Jira automation rules, richer analytics across contracts, and tighter integration with team-specific operational processes—all while maintaining a clear focus on reliability and transparency.
❤️Try it Out
🖐️Demo Configuration
For demo and evaluation purposes, CreatorDeal relies on LLM-based extraction (Gemini or OpenAI) to accurately parse creator contracts. An API key is required to enable this functionality.
While the system architecture includes deterministic extraction as a fallback design, the LLM-based pipeline is the primary extraction path demonstrated in this submission. Without LLM configuration, extraction accuracy is significantly reduced and the core workflow generation experience may not reflect the intended behavior.
✋Demo Contract
💡To try the app, copy the full contract text below and paste it directly into the CreatorDeal intake form.
👌This contract is fictitious and provided solely for demo and evaluation purposes.
➡️ This sample contract is fictitious and provided solely for demonstration and testing purposes. It does not represent a real agreement and should not be used as a legal template.
——————————————————————————————————————————
Ongoing UGC Performance Growth Campaign
Independent Contractor Agreement (V1.5)
This independent contractor / consulting agreement (the “Agreement”) is made and entered into as of December 22, 2025 (“Effective Date”), by and between NovaSpark Digital Inc. d/b/a Studio Flux (the “Company”) and Jordan Lee (the “Contractor”).
- Contractor Personal Information (For Identification & Communication Purposes)
The Contractor agrees to provide accurate personal information for the purposes of contract execution, communication, payment processing, and campaign coordination.
Contractor Full Legal Name:Jordan Lee (Fictitious Name – Demo Use Only)
Email Address:jordan.lee.creator@demo-mail.example (Fictitious Email)
Primary Contact Phone Number:+1 (628) 123-5678 (Fictitious Number)
Country / Region of Residence:United States (Sample Data)
The Contractor confirms that the above information is provided solely for contractual and operational communication related to this campaign.
- Scope of Work 1.1 Campaign Platforms
The platforms designated for this campaign are:
☑ TikTok
☐ YouTube
☐ Other: ___
The selected platforms are collectively referred to as the “Campaign Platforms.”
1.2 Cross-Posting
The Contractor shall post each approved video across all designated Campaign Platforms, unless otherwise specified in writing by the Company.
Cross-posting the same content on multiple platforms constitutes a single deliverable. For each designated platform where the video is not posted, no payment shall be made.
Initial here to confirm understanding of the cross-posting requirement: JL
1.3 Dedicated Campaign Account Information
TikTok Account
Account Username: @flux.jordanugc
Account URL/Link:https://www.tiktok.com/@flux.jordanugc
Instagram Account
Account Username: @flux.jordanugc
Account URL/Link: https://www.instagram.com/flux.jordanugc
The Contractor confirms that these are newly created Dedicated Campaign Accounts established solely for this campaign and acknowledges that these accounts are Company property from inception.
Initial here to confirm accuracy of the account information: JL
1.4 Contractor Obligations
The Contractor agrees to:
Create and maintain new account(s) on the Campaign Platforms solely dedicated to this campaign;
Warm up all accounts using Company-provided procedures prior to posting;
Produce and post original, high-quality video content aligned with Company branding, voice, and campaign objectives;
Share five (5) viral video example links weekly related to the campaign to inspire the community; and
Follow all posting schedules, approval processes, and deliverable requirements outlined herein.
1.5 Campaign Delivery Cap
The maximum flat-fee budget per two-week posting period is USD $1,000 for up to twenty (20) approved videos.
Each posting period shall be a fixed fourteen (14) day cycle.
Videos submitted after the Campaign Cap is reached are not eligible for flat-fee payment. Initial here to confirm understanding of delivery cap and posting period: JL
- Posting Schedule, Tiers, and Delivery Rules 2.1 Tier Assignment
Assigned Tier: Tier 2
Duration: Two (2) Weeks
Tier Definitions:
Tier 1 – Five (5) videos per week
Tier 2 – Ten (10) videos per week
Tier 3 – Fifteen (15) videos per week (flexible)
- Compensation and Performance Bonuses
3.1 Base Compensation
Per-Video Flat Fee:The Company shall pay the Contractor a flat fee of USD $50 per approved video.
3.2 Performance-Based Bonus Eligibility
Performance bonuses are calculated based on total organic views recorded exactly seven (7) days after posting:
Views per Video
Bonus Jordan LeeAmount
5,000 views $10
20,000 views $25 50,000 views
$50 100,000 views
$100 500,000 views
$500
1,000,000 views $1,000
3.6 Organic Performance Only
Bonuses are calculated solely from organic views. Paid advertising, boosted posts, Spark Ads, or any artificial traffic sources are excluded.
Initial here to confirm understanding of Organic Performance Only requirement: JL
- Governing Law and Jurisdiction
This Agreement shall be governed by and construed in accordance with the laws of the State of Delaware.
Signatures
Company Representative
Name: Daniel Roberts (Fictitious)
Title: Director of Creator Operations
Signature: __________________
Date: December 22, 2025
Contractor
Name: Jordan Lee
Signature: __________________
Date: December 22, 2025
——————————————————————————————————————————

Log in or sign up for Devpost to join the conversation.