Submission Rules

Eligibility

This hackathon is open to Bangladesh-based participants only for this run. You must be able to receive payment via standard cross-border methods.

• Participation is individual or in teams of up to 3 people.
• One submission per person or team.
• Team members must be based in Bangladesh and able to receive payment individually.
• You may choose only one track.

Team submissions

If you submit as a team:

• Each member must submit a separate individual contribution statement (max 200 words) describing their specific role and work
• Contribution statements are submitted individually, not as a shared document
• Trial project invitations are made to individuals, not teams. Strong individual performance within a team may lead to an invitation; team membership does not guarantee it
• All team members must be listed at application stage. Changes after application are not permitted

Submission format

All submissions must follow the required format. Submissions that deviate significantly from the format may be marked down or excluded from evaluation.

Required components

• Problem statement — Clear articulation of the specific problem you are addressing (max 300 words)
• Solution overview — Your proposed approach and why it is appropriate (max 500 words)
• Trade-offs and constraints — What you chose not to do and why (max 300 words)
• Business case — Who pays, why, and how this creates value (max 400 words)
• Technical approach — How you would build this, including AI usage where relevant (max 500 words)
• Assumptions and risks — What must be true for this to work (max 300 words)
• Working artefact — A proof-of-concept demonstrating your approach. This is required, not optional. Production readiness is not expected. Scope control is scored. See track-specific guidance below.
• Video walkthrough — A 5 to 7 minute screen recording with voice narration. Walk through your artefact, explain your reasoning, and discuss trade-offs. No slides required. No editing expected. Low production quality is acceptable. Clear thinking is not optional. Submit as a Google Drive link with view access enabled.

Optional components

• Data analysis or market research
• Technical architecture diagram
• Financial model

Optional components are not required but may strengthen your submission if they demonstrate clear thinking. Polish is not rewarded over substance.

Track-specific artefact guidance

The form of your proof depends on the problem. What matters is that something runs.

Track A: Boring Businesses, Real Leverage

A working script, automation, internal tool, or operational workflow. Examples: a scheduling optimiser, an inventory alert system, a process automation.

Track B: From Data Exhaust to Revenue

A data pipeline, dashboard, analysis output, or data product prototype. Examples: a working ETL flow, a decision-support dashboard, a packaged insight report.

Track C: AI-First Products With Long Horizons

A constrained prototype, agent flow, or validated design with limited working elements. Full production is not expected given domain constraints. Examples: a scoped agent demo, a workflow with human-in-the-loop, a validated information retrieval system.

Track D: Automated Internet Businesses

A working system or near-working system demonstrating core automation. Examples: a content pipeline, a lead generation flow, an automated service delivery mechanism.

If your artefact does not fit these patterns, explain why in your submission. Judgement about appropriate scope is part of what we evaluate.

Scoring rubric

Submissions are evaluated across five dimensions. Each dimension is scored 1 to 5, with 5 being exceptional.

Prize

First place: £250

For team submissions, prize money is split equally among team members.

There are no second or third place prizes. Prizes exist to establish seriousness, not to drive participation. The primary incentive is access to paid trial projects.

AI usage

AI tools are permitted and encouraged where they create leverage. However:

• AI-generated content that replaces thinking will be obvious and marked down
• We are evaluating your judgement, not your ability to prompt
• Use AI to accelerate work, not to avoid it

Deadlines

Submission window: 14 days from receiving the challenge pack. Submissions must be received by the published deadline. Late submissions will not be accepted. Dates will not shift once published.

Questions

If you have questions about rules or requirements, check the FAQ first. For questions not covered there, contact us at hello@jambolabs.io.