Cestwise - Sell Project

Cestwise — household planning and retail intelligence software assets 5 November / noviembre 2026 · https://cestwise-technology-opportunity.ramirolosadag.chatgpt.site Problem and buyer value Cestwise connects household food planning and shopping preparation with retail and brand intelligence tooling. Buyer value comes from reusing existing code and domain rules where scope and adoption work fit the buyer’s business. B2C: meal plan to useful output Household, people, preferences and recipes → calendar and portions → aggregated ingredients → pantry reconciliation → shopping list → basket comparison → document. A controlled case uses real functions and synthetic data, persists 2 units and calculates a EUR 4 fixture basket. Session and persistence are mocked; the harness performs mappings into optimizer and PDF. No complete authenticated browser → Supabase → retailer E2E is claimed. B2B: references and costs into analysis Company/brand portfolio → authorized reference data → normalization and calculation → indices, margins and analysis → API or CSV/XLSX/DOCX. Two controlled cases produced six real files, opened afterwards. Account, database and RPC are injected; this is not customer revenue or a full B2B SQL test. Functions and platforms Recipes and search; profiles/preferences; calendars/nutrition; lists/pantry; receipts/OCR; deterministic basket comparison; ingestion/cart adapters; brand portfolios; price indices/history; costs/margins/simulation; API/documentation; reports; AI-assisted text/voice/images; provenance; access/admin; licensing/payments and jobs. Web, Expo mobile, Tauri desktop and extension code exists; release/distribution and acceptance need platform-specific validation. Provider AI models are external; no proprietary trained foundation model is offered. Evidence and limits 328 distinct selected unit cases passed across 43 files. Diagnostics, six real HTTP responses and SQL checks are counted separately. Local PostgreSQL 17 exercised four tables and 15 metadata-derived policies using synthetic identity: not a complete Supabase restore or JWT validation. This is not global coverage or security certification. Samples are explicitly synthetic. Code, rules and know-how Subject to substantiated rights and an agreed inventory: proprietary implementation, API contracts, schemas/migrations, portion/assignment rules, normalization, basket costing, matching, indices/margins, parsers/adapters, templates/renderers, tests and operating documentation. Shared code and third-party models/SDK/solver rights are reserved. User records, credentials and unsubstantiated third-party corpora are excluded. Domain, brand, images and accounts require separate evidence and agreement. Conditional development savings Compatible TypeScript/Postgres B2B buyer with identity, hosting and authorized catalogue: central rebuild estimate of those modules 728 h less 208–416 h of adoption leaves 312–520 potentially avoided hours (about 9–15 person-weeks at 35 productive h). Engineering scenario, not measured savings or promised elapsed time; actual savings can be zero or negative. Do not sum shared modules or overlapping AI/data scenarios or convert hours into an asking price. Method supplied by the owner The EN-17 opportunity framework evaluates market, competitive advantage, timing, scope, team and exit. The supplied workbook is qualitative, with no valuation formulas or weights. Labour savings are assessed against integration, rights and acceptance work. Nova, CTI and other companies in the source materials are teaching/pitch examples, not Cestwise transaction comparables or evidence of its value. Ratios and market references Owner-declared collected revenue: EUR 0. MRR, ARR, profit, margin, paying customers, retention, CAC, LTV and reconciled monthly costs remain undetermined. No revenue/profit multiple is asserted. Profitable-business transaction reports and strategic acquisitions inform context and buyer fit; without comparable price, metrics and asset scope they do not establish a value for this pre-revenue asset. Work before complete operational handover Resolve unit/data consistency, mobile contracts, uniform licensing controls, idempotency and job states. Complete isolated authenticated backend acceptance, restore/Storage, authorized provider, payment sandbox, operating cost reconciliation and client builds/distribution. Verify title/dependencies and agree acceptance tests and bounded transition. Sensitive technical details remain in controlled diligence. Version and transaction status Local audit: c10b7dfb, 5 November 2026. Verified public deployment: 4545109; local changes are not deployed. Declared owner: Ramiro Losada Gómez, individual, Spain. Defined asset acquisition or agreed licence; price open to discussion. No accepted offer or substantiated market valuation. An external estimate is another negotiating reference alongside the audit and actual offers. Contacto / Contact: Ramiro Losada Gómez · hola@cestwise.com