Technical distinction
Auditable, deterministic forecasting
Forecast inputs, historical comparators and calculation rules can be inspected. Language models do not invent operational quantities.
👋 Welcome to Annambox
We help bring the orders.You cook & deliver.AKIE helps you plan.
Serve shift workers through the planned Annambox marketplace—and manage your own takeaway orders on the proposed kitchen platform. Your team cooks and handles delivery or collection; AKIE helps plan what to prepare and buy.
Marketplace and independent takeaway tools are planned · Partner-kitchen pilots are being explored
How a partner kitchen could workIllustrative example
🛍️✓
1 · Shift workers order
62 boxes paid for
🍲✓
2 · AKIE makes the plan
Dish batches calculated
🥬✓
3 · Kitchen gets ready
Ingredients & shopping gaps
Visual demonstration, not a live feed or measured performance result.
How Annambox works
Three steps. One clear kitchen plan.
📱
Orders come in
Marketplace orders or your own takeaway orders.
🧠
AKIE plans
Forecasts and batches by shift.
👩🍳
Cook & deliver
Your kitchen prepares and fulfils orders.
Want to see the technology behind the plan? ⌄Explore AKIE's forecasting, technical approach and evidence.
Who we are
A planning engine for kitchens serving fixed shift windows.
Annambox began with a meal-service pilot serving shift workers in Bristol. Working around order cutoffs and fixed collection windows revealed how closely customer demand, kitchen preparation and ingredient purchasing are connected.
Taking orders is only the starting point. A kitchen must decide how much to prepare, which dishes to batch, and whether ingredients will be available before the shift collection window. AKIE models those connected decisions. Our next step is validating the engine with independent commercial kitchens.
The Bristol shift-meal pilot generated operational order history that informs AKIE development. That meal service has ended; independent partner-kitchen pilots are the next stage.
The technology
The innovation: a paid-order demand floor connected to kitchen execution.
AKIE starts with a non-negotiable constraint: a kitchen must not plan fewer portions than customers have already paid for. Its deterministic AB-FORECAST-0.3 engine uses confirmed demand as the floor, then combines comparable historical shifts to estimate possible additional demand. The estimate feeds dish batches, recipe quantities and purchasing checks. The calculations are intended to be traceable to data and rules, not generated by a language model. Third-party performance still needs validation.
AKIE decision flow
Shift-specific · Evidence-led01
Paid orders
Non-negotiable demand floor
02
Forecast
Estimate demand above floor
03
Dish batches
Production quantities
04
Ingredients
Recipe × portions
05
Procurement
Stock gaps & purchases
Worked example · Illustrative, not actual pilot results
62 paid portions. What should the kitchen prepare?
CONFIRMED FLOOR
62
Already paid for
ILLUSTRATIVE FORECAST RANGE
88–96
Possible final portions
NEXT DECISION
Batch + stock plan
Translate dish mix into ingredients and gaps
The forecast never erases the 62 confirmed orders. The kitchen uses the estimated additional demand, recipes and available stock to review a preparation plan. All numbers in this example are hypothetical.
Evidence dashboard · Results pending verification
Forecast error versus last-week baseline
A verified historical replay will report forecast portion error, baseline error, sample size and cutoff timing here. We are deliberately withholding performance percentages until the underlying backtest is independently checked.
Technical distinction
Shift-level constraints
A fixed collection window creates a different planning problem from continuous restaurant demand. The system works with service days, shift types and production cutoffs.
Next-stage engineering
Capacity-aware kitchen networks
Kitchen capability and readiness modules exist in code. Automated cross-kitchen assignment remains a development and validation objective, not a live service claim.
Shift-aware demand planning
Combine historical demand and advance orders to support preparation decisions around fixed service windows.
Production intelligence
Translate meal demand into dish-level preparation quantities and recipe-based ingredient requirements.
Inventory and procurement
Connect ingredient requirements to stock information and purchasing recommendations, with checks where stock is uncertain.
Operational evidence
Use historical orders, forecasting backtests and controlled simulations to evaluate decisions rather than assume performance.
Competitive positioning
How AKIE is positioned differently.
Kitchen inventory, recipe costing, restaurant forecasting and order-management products already exist. Our proposed differentiation is the integration of shift-bound preorders, a confirmed-order minimum, dish batching and ingredient-to-purchasing decisions for smaller kitchens serving fixed workplace windows. This is a product positioning hypothesis to test against alternatives, not a claim that no competitor offers overlapping functionality.
General inventory software
Often starts with stock and purchasing. AKIE starts with the shift's paid orders and carries demand through to ingredient requirements.
Restaurant order management
Typically connects ordering channels and fulfilment. AKIE focuses on advance batch-preparation decisions before a fixed collection window.
Kitchen forecasting platforms
Forecasting overlaps with existing products. AKIE's testable proposition is a single workflow that respects confirmed orders and shift-specific production constraints.
Founder and execution
Software engineering meets kitchen operations.
Annambox was founded by Vineeth Reddy Kottakapu, an MSc Computer Science graduate with a background in full-stack development and practical kitchen and warehouse operations.
The product combines a Next.js and TypeScript interface, a Supabase/PostgreSQL backend and a growing library of deterministic demand, forecasting, recipe, inventory and simulation modules. Git history and reproducible tests can be used to demonstrate technical development.
The product draws on both software engineering and firsthand experience of shift-based meal preparation and fulfilment.
Commercialisation hypothesis
A repeatable kitchen software model.
Annambox proposes a subscription for each independent kitchen, with usage-based fees linked to boxes processed. An optional marketplace could later charge for orders it originates. Commercial terms are indicative and subject to agreement; the independent-kitchen SaaS model is not yet generating revenue.
Scaling depends on successful kitchen pilots, secure multi-tenant software, customer acquisition and hiring across engineering, onboarding and support. Growth will depend on demonstrating value to early kitchens and building a repeatable onboarding and support process.
One kitchen · Two ways to grow
Your kitchen. Your customers. More ways to take orders.
Partner kitchens could use Annambox to serve workplace shifts and manage their own takeaway trade. Both routes connect to kitchen planning, while each kitchen remains responsible for preparing and fulfilling orders.
Route 01 · Planned marketplace
We help connect you with shift workers.
Worker orders→Your kitchen cooks→You deliver / arrange collection
Annambox plans to attract and coordinate workplace meal demand. Partner kitchens prepare and fulfil accepted orders. Customer acquisition and order volume are not guaranteed.
Route 02 · Proposed kitchen SaaS
Keep running your own takeaway.
Your customers→Your orders & menu→Your fulfilment
The proposed partner platform will let kitchens manage their own takeaway ordering and kitchen planning alongside any Annambox-sourced orders, without depending on marketplace demand.
AKIE supports both routes.
Confirmed orders → dish batches → ingredient quantities → purchasing gaps
Partner marketplace, takeaway-management and integrated fulfilment workflows are proposed capabilities for independent kitchens, subject to pilot development and validation. Each participating kitchen remains responsible for food safety, legal compliance, delivery and collection arrangements.
Why kitchens join
Plan for the shift, from paid order to ingredient list.
Know what to cook before you cook it.
Shift workers pay ahead, so every paid order is a confirmed portion. AKIE treats that number as the minimum and builds the plan from there.
Turn orders into a shopping list automatically.
Paid orders feed dish batches, recipe-based ingredient quantities and purchasing gaps, without a separate spreadsheet between each step.
Built for the shift window, not the dinner rush.
Collection times and order cutoffs are fixed. Plan preparation for a known service window instead of relying on walk-in demand.
Founding kitchens shape the product.
Early partners can give direct feedback to the founder and help prioritise the next features during pilot development.
Pricing that scales with you
Simple indicative pricing for kitchen partners.
£75 / kitchen / month
Platform and maintenance
£0.30 / box
Charged only on boxes processed
Illustrative example: 1,000 boxes in a month would cost £375 in total, equivalent to 37.5p per box. Pricing is for discussion only, not a binding offer.
Enquire about a kitchen pilot →Our business model
Join the founding kitchen pilot.
AKIE SaaS: Our proposed subscription product will let partner kitchens manage their own takeaway orders, menu and operational planning independently.
Optional marketplace: We plan to connect workplace customers with participating kitchens. Kitchens will prepare, pack and arrange delivery or collection, while Annambox proposes to provide marketplace ordering and coordination technology.
We are inviting appropriately registered commercial kitchens to discuss a founding pilot. Pilot scope, duration and commercial terms will be agreed individually. Indicative pricing is for discussion, not a binding offer. The marketplace and independent-kitchen SaaS rollout, including takeaway-management workflows, are planned, not yet operational.
Enquire about a kitchen pilot →Our direction
Our roadmap: validate, pilot, connect.
Stage 1 — Validate: replay historical shifts and compare forecast portion error against a last-week baseline. Stage 2 — Pilot: test AKIE workflows with registered independent kitchens and measure operational usefulness. Stage 3 — Network: develop capacity-aware allocation across participating kitchens, subject to technical and commercial validation. No waste-saving or accuracy result is claimed until measured.