Sell appointment software under your own brand

Two ways to work together

The right one depends on whether you want to own the infrastructure or stay out of it entirely.

• White-label reseller

  You sell, I host and operate. Your brand in the product, your pricing, your support desk. You are billed per active business, on a recurring basis, and I never contact the businesses you sign. Fastest path: nothing to deploy and nothing to maintain on your side.

• Licensed deployment

  The platform is installed into infrastructure you own, under your accounts. You hold the data, the keys and the store listings, which answers the procurement question that ends most deals with a small vendor. Priced as an implementation plus ongoing maintenance.

What the platform already does

None of this is a roadmap item. It is shipped, in daily use, and you can open it before we talk.

• Booking, three ways in

  Staff book from the management app, clients book from their own app, and anyone can book from a public page without installing anything. Availability is per professional, with holidays, time off and service duration respected.

• The money side, not just the calendar

  Open tabs, products and packages, cash opening and closing, accounts payable, supplier records, stock movement and commission per professional and per service, with reporting over all of it. This is the part competitors leave out and owners ask for first.

• Automated appointment reminders

  Reminders go out on WhatsApp on a schedule, prepaid by the business. The sending job is split into a dispatcher and a worker, so a slow provider delays one message instead of the whole run, and a retry cannot send the same reminder twice.

• Two mobile apps, one codebase

  A management app and a client app, published separately from the same repository through build flavors, plus the web version of both. A new brand does not mean a new codebase.

• A public marketplace

  Businesses that opt in get a public profile and show up in a searchable directory with its own indexable pages. For an agency, that is a second reason for the client to stay.

• Tenant isolation enforced by the database

  Each business owns a subtree of the database and the security rules resolve the caller against the organisation in the path. Billing and subscription fields reject any write coming from a browser, no matter who is signed in.

Already built for a market outside Brazil

• Interface in three languages

  Portuguese, English and Spanish, with no hardcoded strings anywhere in the product. Adding a fourth is translation work, not engineering work.

• Country, currency and time zone per business

  Each workspace stores its own country, currency and time zone when it is created. Currency is persisted separately from country on purpose: amounts already recorded must never change denomination because a setting was edited.

• Per-business theming

  Colours are resolved per workspace and per sector, so the marketplace and the client-facing screens already carry different identities rather than one fixed palette.

• Commission tracking for the partner

  A partner module already computes commission in basis points over amounts held in minor units, and closes a period into an immutable record. Attribution cannot be rewritten after the fact, which protects both sides of the deal.

What gets built for your market

The honest list. These are not hidden gaps, they are the parts that only make sense to build once against a real market, and they are scoped into the engagement.

• Local payment and recurring billing

  Subscriptions are collected today through the mobile store billing system, and the only direct payment method wired in is the Brazilian instant transfer network. A card gateway on the web, under your merchant account, is part of the work.

• Your own messaging sender

  Reminders currently leave from a single approved business number. A white-label brand needs credentials per tenant so messages arrive from you, not from Marksym.

• Your domain, your listings, your sender

  Custom domain, logo, transactional email from your address and your own entries in the app stores. Mechanically straightforward, but it needs your accounts and your legal entity.

• Sector-specific fields

  The data model was shaped by appointment-based businesses. Adjacent sectors usually need a handful of fields and one or two rules, not a rewrite.

Not a prototype

Counted straight from the repository every time this page is built. Due diligence on a small vendor usually starts here.

• 181,000+lines of Dartacross 452 files in the app layer
• 21,000+lines of TypeScriptbackend running on managed infrastructure
• 1,800+automated testsrun before anything ships
• 46backend endpoints38 callable, 3 webhook, 5 scheduled
• 2,646translation keysmaintained in three languages

How it starts

No commitment until the third step, and nothing to install before it either.

1. A call

   Which sector you serve, how many businesses, and which of the two models fits. Thirty minutes is usually enough to know whether this is worth continuing.

2. A workspace in your name

   I set up a live tenant with your branding and real data you provide, so you demo the product to your own clients instead of reading about it.

3. Scope and terms

   What gets built for your market, in what order, and how the commercial side works. Written down before anything is signed.

4. A pilot

   A small group of your clients goes live first. Support load, edge cases and local expectations surface here, while they are still cheap to fix.

5. Rollout

   The rest of your base, at your pace. You own the relationship the whole way through.