Scheduling, Records & Patient Flow
Unified appointments, intake, digital encounters, and patient records operating seamlessly in seven languages.
We start with private outpatient clinics: one workflow for scheduling, records, communications, claims and payments. The same identity, workflow, AI, communications and financial infrastructure can support additional vertical products over time.
CUBE OneCare with integrated payments is our wedge. It connects clinical, operational, and financial workflows for private outpatient ambulatory clinics, medical centers, and independent physicians.
Unified appointments, intake, digital encounters, and patient records operating seamlessly in seven languages.
Clearinghouse-connected insurance claims, automated eligibility, and contactless patient pay via Stripe Connect under active commercial contract.
Built for HIPAA from day one: our clearinghouse BAA is signed, and our hosting BAA will be signed before any real patient data enters the platform.
Private clinics face fragmentation at every step: separate tools for booking, EHR, clearinghouses, communications, card terminals, and bank reconciliation.
Staff copy-paste patient details between scheduling software, medical record apps, clearinghouse portals, SMS tools, and external card readers.
Visits, charting, communications, claims, and cardholder payments move through one coherent operational layer with progressive module adoption.
We state traction, readiness, and maturity with absolute discipline. No hypothetical milestones.
Our first U.S. outpatient clinic implementation is underway. The environment currently uses synthetic data and will remain gated from real patient data until the required hosting BAA is executed.
Our first merchant account is activated in production and preparing for its first live transactions.
Five CUBE products have material implementation. CUBE Assembly + Home remains pre-build.
Our immediate milestone is converting the first OneCare and simpleTap implementations into sustained paid usage.
OneCare is CUBE's first commercial wedge. Underneath it, CUBE reuses the infrastructure that is expensive to rebuild in every product: identity, permissions, workflows, communications, AI, payments and operational evidence.
Organizations, users, roles, access and tenant boundaries maintained across products.
States, automation, tasks, approvals, and immutable audit evidence.
Messaging, telephony, WhatsApp, and workflow-linked patient/merchant notifications.
Model-agnostic intelligence with strict prompt containment, policy, and human release controls.
Payments and financial-provider orchestration through eligible external rails and Stripe Connect.
Reuse does not mean mixing products together. Each product keeps its own customers, launch gates, contracts, evidence and economics.
The portfolio is a sequence — not six simultaneous launches. Capital follows proof.
Practice operations SaaS for private outpatient clinics and independent physicians. Software licenses + clinic patient pay via Stripe Connect.
Designed as a generic NFC point of sale for Android, direct to merchants: in-person contactless, QR and payment-link acceptance.
CUBE's unified API for financial orchestration and its ledger, on the same Stripe platform. Sandbox; no live money yet.
Fitness business operating system. Management platform, memberships, and facility scheduling requiring launch QA.
A commerce SaaS with a unified print-on-demand API (white-label storefronts on a POD network). In development; not live and not onboarding connected accounts.
CUBE Assembly is what we're building for people who build software. Ask CUBE is what we're building for everyone who uses CUBE. It's pre-build, and CUBE is its first customer.
Each product must earn commercial proof independently. Shared technology does not substitute for product-level evidence.
Multiple compounding revenue streams grounded in software value and transactional flow. The portfolio works only if shared primitives reduce release cost while every product retains separate contracts, liability, evidence, P&L and launch gates.
Monthly and annual seat licenses for practitioner clinical desks, administrative seats, and merchant terminals create the base layer.
Usage-based intelligence, high-throughput voice, automated transcription, APIs, compute and managed operations expand with verified use.
Platform application fees and contractually agreed partner economics on completed patient and merchant card transactions processed via Stripe Connect. TPV, GMV and pass-through funds are not CUBE revenue.
No live creator marketplace, third-party supply, sales or payouts are claimed today; provider commerce and a governed no-code module economy remain future, gated extensions with no live marketplace claimed.
CUBE Core and CUBE Browser are selective donors for CRM, CSM, ERP, HR, POS, mail, documents, workflow, AI and other industry patterns—not products to relaunch.
Felix Parentini, CUBE's co-founder and CTO, leads architecture and directs CUBE's AI-assisted engineering.
We continuously evaluate different frontier and open model families instead of tying engineering to a single vendor.
Deterministic test coverage, strict regression gates, and automated preflight validation across repositories.
AI accelerates implementation throughput. Architecture, acceptance criteria and final release decisions remain under founder control.
External agreements, BAAs, provider approvals and country permissions have their own clocks. CUBE does not relabel those dependencies as finished engineering.
Implement OneCare and simpleTap pilots. Close Atlas, HARDWON and Kadolia public/market-facing refactors. Establish Assembly + Home charter and creator rights.
Capture early pilot evidence, close Atlas V1, pass HARDWON/Kadolia QA and run Assembly internal alpha with Home across two products.
Convert pilots toward paid use, open OneCare creator closed beta, validate first Atlas route and measure Assembly release savings.
Institutional Atlas if gates pass; Assembly private beta; cross-product Home; curated marketplace only after IP, payout and moderation controls.
OneCare hospital and complex-care depth, multi-region Atlas and broader creator economics—always tied to contracts, control evidence and unit economics.
Biographies provided and confirmed by each executive on October 2, 2026.
Co-Founder & Chief Executive Officer
Leads CUBE's commercial strategy, partnerships and fundraising. Commercial real estate finance experience managing originations, underwriting, and client development across institutional transactions.
Co-Founder & Chief Technology Officer
Leads architecture and directs CUBE's AI-assisted engineering. Over two decades architecting distributed high-availability platforms, systems engineering, and release discipline.
Co-Founder & Chief Financial Officer
Leads finance, capital structure, reporting and Latin American operations. Former Director General of INEN (national standards institute), directing audit frameworks and international technical agreements across cross-border trade.
Structured to implement two first pilots, close three market-facing products, and build the Assembly + Home internal alpha.
Offering to verified accredited investors through Wefunder. All terms, disclosures, documentation, verification and subscription are managed exclusively through Wefunder.
Activate, instrument and reconcile the first contactless/QR pilot.
Complete first outpatient pilot implementation, evidence, licensing and governed ecosystem foundations.
Build the internal alpha, Trust Fabric, dual-product Home and creator foundations.
Close frontend/public refactor, product UX, docs, sandbox, QA and first-route readiness.
Complete market-facing refactors and evidence-based launch gates.
Support contracts, provider paths, corporate work, controls and execution reserve.
Offering to accredited investors whose status is verified through Wefunder before they invest.
Review verified non-binding expressions of interest, architecture specifications, and governance filings.
Signed strategic expression of interest for private ambulatory clinic implementation (CUBE OneCare).
Signed strategic expression of interest for Latin American financial orchestration corridors (CUBE Atlas).
Complete 15-slide interactive presentation covering portfolio sequencing, financial architecture, and product depth.
Ten high-definition commercial spots and architectural breakdowns across the product suite.
Retired OneCare/Atlas decks and earlier investor materials are not published in this investor library. Current materials use the unified CUBE platform thesis and the October 2, 2026 maturity labels.
Each mode uses the same maturity and financing boundaries. The difference is how much time the investor has—not which facts CUBE presents.
Technology fragments identity, AI, workflows and transactions. CUBE is building one governed operating matrix across six products and three clusters—five materially implemented, two pilots underway, CUBE Assembly + Home pre-build.
Care and human performance: CUBE OneCare + HARDWON. Money movement and financial infrastructure: simpleTap + CUBE Atlas. Creation, commerce and distribution: Kadolia + the planned CUBE Assembly + Home. Shared rails can compound; maturity, liability and economics stay separate.
Identity, multi-model AI, workflow orchestration, communications, and money movement built once and safely reused without mixing product liabilities or accounting.
Offering to verified accredited investors via Wefunder. Review offering documentation, terms, and progress on our official Wefunder page.
Biographies provided and confirmed by each executive on October 2, 2026.