01DISCOVER
Find the useful signal.
Tell us about your business, your data, and the expertise behind it. Together, we identify material that could be useful to AI teams.
REAL WORK. REMARKABLE DATA.INDEPENDENT KNOWLEDGE. SHARED PROGRESS.
The next leap in AI
starts with your data.
The work your company does every day holds knowledge AI hasn’t learned. Jog helps you turn it into a new source of value.
Estimate your data’s valueLooking for data? Meet Jog.BUILT FROM EXPERIENCELICENSED WITH INTENTMADE FOR WHAT’S NEXT
01 / THE OPPORTUNITY+
Some of the world’s
most useful knowledge
isn’t on the internet.
It’s in the problem your team solved. The review that caught a mistake. The steps between a question and a good answer.
These records give AI something public data can’t: a view of how real work gets done. Jog connects the people who hold that knowledge with the teams who need it.
02 / THE KNOWLEDGE YOU HOLD+
Already created.
Not yet realised.
Useful data is already in the tools your team uses. Explore the records, decisions, and finished work that could have a second life.
DATA TYPECONTEXT & SOURCE TOOLSEXPLORE
01ConversationsThe reasoning behind the decision.SlackMicrosoft TeamsGmailOutlook
Project discussions, support exchanges, and internal threads show how people work through ambiguity and reach a useful answer.
EXAMPLES
02Code & engineeringThe journey from problem to working software.GitHubGitLabBitbucketJira
Repositories become richer when paired with issues, reviews, tests, and the decisions that shaped each change.
EXAMPLES
03DocumentsExpertise, written down and put to use.Google DriveNotionSharePointDocuSign
Working documents capture both an organisation’s knowledge and how that knowledge develops through drafts, reviews, and revisions.
EXAMPLES
04Business recordsThe structured picture of how a business runs.SalesforceHubSpotQuickBooksXero
Well-documented tables and records can connect business activity to real outcomes, giving models grounded examples to learn from.
EXAMPLES
05Completed workflowsThe full story, from brief to result.ZendeskAsanaServiceNowLinear
A finished task becomes more useful when it includes the original request, intermediate work, feedback, and the accepted result.
EXAMPLES
06Expert knowledgeThe judgement that experience builds.ExcelGoogle SheetsJupyterConfluence
Worked examples, annotated decisions, and expert assessments make the subtle parts of a profession easier to understand and evaluate.
EXAMPLES
These tools are examples of where useful data can live. Start with a description of data you can license; no account connection is needed.
ONE WORKFLOW. MORE OF THE STORY.
A solved problem leaves a useful trail.
For example, a software support issue can connect a customer question to the decision, the fix, and the result.
- 01 / ZENDESKThe questionA support request and the context behind it.
- 02 / SLACKThe reasoningThe discussion that finds the cause.
- 03 / GITHUBThe solutionA reviewed change, with tests and feedback.
- 04 / NOTIONThe learningA documented resolution the team can reuse.
03 / KNOWLEDGE ACROSS INDUSTRIES+
Every industry has
something to teach.
Specialist work creates specialist knowledge. Here are some of the sectors — and the everyday records — worth exploring.
01
Software & IT
Code reviews, incident reports, migrations, and implementation decisions.
Explore this sector 02Finance & accounting
Reconciliations, close workflows, financial models, and review notes.
Explore this sector 03Legal & compliance
Contract revisions, research trails, policy reviews, and matter workflows.
Explore this sector 04Healthcare & life sciences
Research protocols, lab workflows, quality reviews, and scientific analysis.
Explore this sector 05Manufacturing
Inspection reports, specification changes, production logs, and root-cause analysis.
Explore this sector 06Construction & property
Project estimates, scopes of work, planning revisions, and site reports.
Explore this sector 07Customer operations
Resolved tickets, escalation paths, quality scores, and service playbooks.
Explore this sector 08Sales & revenue
Pipeline histories, quotation approvals, forecasting, and renewal workflows.
Explore this sector 09Marketing & creative
Campaign briefs, creative iterations, experiments, and performance reviews.
Explore this sector 10Recruiting & people
Role briefs, assessment rubrics, hiring workflows, and onboarding guides.
Explore this sector 11Insurance
Claims workflows, policy reviews, risk assessments, and quality checks.
Explore this sector 12Logistics & distribution
Routing decisions, exception handling, fulfilment records, and warehouse procedures.
Explore this sectorYour sector isn’t listed? Start with what you have.
04 / EXPLORE THE POTENTIAL+
What could your
data be worth?
Tell us a little about your company. Explore an illustrative licensing range, then take the next step with a clearer picture.
ILLUSTRATIVE LICENSING RANGE
USD · one potential dataset licence
Adjust the example company to explore a range.
A planning illustration using sample assumptions, not an offer or a market valuation. A real quote depends on the data, permissions, licence terms, and buyer demand.
How is this calculated?
The example model starts at $8,000 for 25 people, 3 years of usable records, and one organised source type.
Team size and history scale by their square roots. Each additional source type adds 18%; raw files use a 0.75× factor and reviewed workflows use 1.3×. The displayed range is 60–150% of that scenario, rounded to $250.
These are illustrative assumptions, not observed market rates. Your sector provides context for an enquiry and does not change the calculation.
05 / A CLEAR PATH FORWARD+
From everyday work
to a new opportunity.
A thoughtful licensing process starts with understanding what you have — and what you want to do with it.
02PREPARE
Make the context clear.
Define the scope, review permissions, and agree what needs to be excluded. Shape the dataset around a clear use case.
03LICENSE
Agree on the value.
Review the buyer’s intended use and proposed terms. Move forward when the scope, price, and agreement work for you.
06 / BUILT AROUND THE OWNER+
Your knowledge.
Your terms.
A data partnership should start with clarity. What’s included, how it can be used, and what you receive in return.
Start with a defined scope.
Choose the datasets and workflows you want to discuss. An initial conversation doesn’t require a full data upload.
Keep sensitive material in view.
Identify confidential content, personal information, and third-party rights before preparing any sample.
Make the intended use explicit.
Set out who can use the data, for what purpose, and under which commercial terms before a transfer.
07 / FOR AI TEAMS+
A world of knowledge.
Beyond the web.
Build with data that reflects the complexity of real work. Tell us what your model needs to learn, and we’ll explore the right sources with you.
More than the final answer.
Find examples with the reasoning, revisions, and decisions that led to the result.
Start with your use case.
Scope datasets around the domains, tasks, and formats your team is working on.
Know where it comes from.
Make source, ownership, and permitted use part of the conversation from day one.
08 / A FEW GOOD QUESTIONS
Let’s make
it clearer.
What makes a dataset useful?
Relevance, quality, context, and permission to use it. Material that records specialist knowledge or a complete workflow can be more useful than a large collection of disconnected files. The fit depends on the buyer’s use case.
Do I need to organise everything first?
No. Start with a description of what you have: the sources, formats, approximate size, and the work it represents. That is enough for an initial discussion. Don’t send confidential files in an enquiry.
How is the price determined?
Pricing depends on the dataset, its quality and uniqueness, buyer demand, and the scope of the licence. There is no fixed payout or guaranteed sale. Any commercial terms would be agreed before proceeding.
Can an individual expert take part?
Yes, the conversation can start with an individual’s expertise, worked examples, or original materials. You need the relevant permissions for anything you propose; access to an employer’s data alone does not establish that authority.
Is this an exclusive arrangement?
Exclusivity, permitted uses, licence duration, and delivery are all terms to discuss for a specific partnership. An initial enquiry does not commit you to an agreement.
Let good work
go further.
Start with a conversation about what you have.