BABAIby NEKURAMA · internal mock
STATIC MOCK / NOTHING SUBMITS

WEB / QA · INVENTED LOCAL STATE

One journey.
Many hands.

A deterministic visual prototype for reviewing how admin, owner, staff and customer moments might connect.

No account, form, payment, customer record, backend, provider or network request exists behind this page.

MOCK 0 external actions

01A / WHY NEKURAMA

Technology should return attention.

NEKURAMA is being shaped around useful, governed software for people who run real businesses—not another layer of noise.

THE MOTIVATIONMake complex work feel human.Clear states, visible handoffs and recovery instead of hidden automation.
THE BELIEFOwn the relationship, not just the transaction.Businesses should keep context, trust and a direct path to their customers.
THE STANDARDUseful before impressive.Every promise must survive operational, economic and human review.

01B / NEKURAMA PRODUCTS

One operating idea. Many useful products.

NEKURAMA is the parent direction. BABAI is the first product being explored in this prototype; future products must earn their place through the same discipline.

NEKURAMAParent company and operating identity.Builds and owns focused products with clear boundaries.
BABAIBusiness automation by AI for restaurants.WhatsApp-first ordering, pickup and human-assisted operations.
THE PRODUCT RULEBounded automation, visible control.No unrestricted AI authority, hidden data use or silent handoff.

01C / BABAI INTRO

A calmer way for restaurants to take orders.

BABAI connects the customer conversation to the restaurant operation while keeping the staff, the order and the next action visible.

RECOVER DEMANDTurn missed messages into structured order intent.Menu, cart, quantity and pickup context stay together for review.
PROTECT THE RELATIONSHIPKeep the direct customer path with the restaurant.Pickup-first flows avoid forcing every customer through another marketplace experience.
SAVE STAFF ATTENTIONAutomate the routine, preserve the human.When a question needs judgment, the collected context moves with the handoff.
MAKE RECOVERY VISIBLEFailures become states to resolve, not surprises to hide.Payment, provider and fulfillment boundaries remain explicit.

01 / THE SCENARIO RAIL

Choose a scenario. Play the conversation.

Choose an operation, then play the WhatsApp-style conversation message by message. Every screen is a local fixture with a visible handoff, boundary or recovery state.

STATIC MOCK / NOTHING SUBMITS Fictional names · statuses · timestamps · prices 90-DAY PAID PILOT / READINESS REVIEW · INTERNAL MOCK

S01 / ADMIN ONBOARDING · MOCK

An invitation finds its owner.

LOCAL READY

MESSAGE 01 / 04

02 / RESTAURANT OPERATIONS

The restaurant runs the business in chat.

One dedicated operations conversation moves from onboarding to menu changes, orders, staff support, delivery handoff, vouchers and weekly insight.

STATIC MOCK / NOTHING SUBMITS Restaurant owner · cashier · staff · delivery partner fixtures RESTAURANT OPERATIONS / INTERNAL MOCK

R01 / ONBOARDING · MOCK

A restaurant starts with a conversation.

ONBOARDING

SCENARIO 01 / 08 · MESSAGE 01 / 06

01A / COVERAGE SLICES

The edges stay named.

Placeholder slices keep the review honest where the story rail is intentionally compact.

STAFF PERMISSIONSOwner → staff → handoffLATER / scoped role placeholder
PROMOS + COMBOSLITE → BASE → PRO gatesPILOT REVIEW / expiry placeholder
ADMIN ANALYTICSFunnel / attention / reconciliationPOC / invented counts only
REORDER + REFUNDReview → recovery → retryPILOT REVIEW / no action sent
14-FLOW INVENTORYSource-mapped journey coverageSee internal QA matrix

02 / INTERNAL EXPERIMENT

Choose a shape, not a promise.

Approved internal pilot and post-pilot pricing direction. It is not public pricing, a checkout or an entitlement decision.

PILOT → POST-PILOT · PRE-GST · INTERNAL MOCK Monthly prices are review anchors; onboarding and provider costs are shown separately in the internal model.

03 / HARD BOUNDARY

A prototype can be vivid without pretending.

STATIC MOCK / NOTHING SUBMITS

No auth. No real form. No payment. No customer record. No backend. No external request. No public claim.

Reset returns the story rail to Invite and the tier experiment to BASE. All fixtures are invented.

04 / CONTACT

Keep the door open. Keep the details honest.

Contact routes are intentionally not connected in this static mock. Public contact details will be added only after ownership, domain and publication approval.

COMPANYNEKURAMAParent company identity · publication details pending approval
PRODUCTBABAIRestaurant automation product · pilot intake route pending approval
CONTACT ROUTESEmail · WhatsApp · pilot formNo address, number or message is collected by this prototype