What we have actually shipped

The month the pricing, the funnel and the whole public site were rebuilt — and the month the AI voice agent got its compliance foundation before it got its dialler.

• Three tiers, everywhere

  Solo at ₹899 per seat per month, Team at ₹749 (₹599 billed yearly) for any number of seats, and Custom CRM quoted after a scoping call. This replaced a four-tier scheme that shipped earlier in the same month and did not survive contact with real buyers — the band structure made the rate step at seat counts nobody could predict. Legacy plans were retired and existing workspaces migrated.

  PricingWebAPISee the rate card

• No free trial, no self-serve signup

  Every call to action on the site is now Get a demo. Workspaces are provisioned by a person on the call rather than by a card swipe, which is slower for you and deliberate on our side — it is how the residency and access model stays true rather than aspirational. The top navigation collapsed from nine items to five at the same time.

  MarketingWebHow the demo works

• A new saudaflow.in — 32 new pages

  A page per product capability, a page per audience, and the resources section this changelog sits in. The homepage went from thirteen sections to eight with body copy cut by roughly 60%, and the illustrations were replaced with real product screens. Region handling was simplified to India-only after the multi-currency work of May turned out to be solving a problem we did not have yet.

  MarketingBrowse the product pages

• AI voice agent — the compliance foundation

  ADR-0064 phases 0 through 3. The disclosure a recipient hears before any recording begins, in the language the workspace has chosen rather than hardcoded English, with consent state stored on the record and the whole thing gated behind DLT registration. Compliance was built first and dialling second, which is the opposite of the usual order and the only order TRAI makes workable.

  APIMobileWebHow the voice agent works

• Mobile parity — 47 of 47

  Every capability in the web workspace is now reachable in the Android app, tracked as a registry with a number attached rather than asserted as a slogan. Six capabilities were ported natively in this wave, including the workspace hub, the firm admin surfaces and the agent earnings screen. The published build is 1.0.0-beta.16.

  MobileWhat the app does

• Cost sheets, from the statute to the phone

  Base rate on carpet area, floor rise, preferential location charge, parking, maintenance deposit, stamp duty, registration and the GST treatment as real line items rather than a template someone retypes. Generated on the phone at the site office and shared to WhatsApp as a branded PDF in two taps. Shipped to installed phones as an over-the-air update rather than a store release.

  WebMobileAPICost sheets

• Brokerage receivables, and the TDS rate we had wrong

  Ageing buckets, payout triggers tied to milestones, clawback, GST handling and an earnings screen an agent can open without asking accounts. We also found and fixed a real error: brokerage was deducting TDS at 10% where section 194H requires 2%. It is listed here because a changelog that only records successes is a marketing page.

  WebAPIBrokerage and TDS

• Role-aware dashboards for all seven roles

  Owner, Admin, Manager, Team Lead, Agent, Site staff and Back-office each get a dashboard built for what they are accountable for, rather than one screen with things hidden. Every ratio now carries its denominator — "100% conversion" on one site visit out of one is how a firm stops trusting a number, and it took an audit to notice we were doing it.

  WebMobileReports and dashboards

• Historical dashboards and the evening MIS block

  Reporting stopped being only about today. Trends run over time, presence is reported honestly rather than optimistically, and the end-of-day summary is laid out to be read on a phone in a car rather than printed. The status bar was rewritten to say what is actually true of a workspace.

  WebMobile

• One lead, many projects

  A buyer looking at three towers is now one record with three interests, not three duplicate leads that three agents call separately. This was the front end that the CRM restructure had specified and never received, and it is the single change that most reduced double-calling in the demo workspace.

  WebAPILead management

• Portal listing syndication framework

  Built, not switched on

  The framework for publishing inventory out to 99acres, MagicBricks and Housing, and for taking the resulting leads back in deduplicated. It is built and it is not switched on. Until it is, portal leads reach SaudaFlow the way they reach everyone else — email parsing, a shared inbox or a CSV — and every page on this site that mentions portals says so in these words.

  APIIntegrations

• Row-level security, proven rather than assumed

  Seven tenant tables were found with row-level security switched off entirely, and it was switched on with a test that proves one workspace cannot read another. The first automated CI gate landed in the same wave, along with a migration set that could finally apply cleanly from zero. This is unglamorous and it is the most important entry in this month.

  APISecuritySecurity posture

• Signup that forks by tier, and trials that end

  One signup path that branches on which product you are buying, trials that actually expire instead of quietly continuing, and operator provisioning in the admin portal so a workspace can be created on the demo call. Also five separate funnels that were silently losing leads, which is an embarrassing thing to find in a lead management company.

  WebAPI

The mobile month. Call sync, over-the-air updates, and the access model that scopes a lead to a person rather than a company.

• The firm, admin and agent model

  Every lead read and write is now scoped to the caller rather than to the workspace, which is the difference between "your company can see this" and "you can see this". Privacy masking, seat and rights management, firm chat and an inventory visibility model landed alongside it. Eleven lead-bearing routes were found returning more than the caller should have seen, and were closed.

  APIWebSecurity

• Android call sync, natively

  A post-call sheet that opens the moment a call ends, capturing the disposition, a typed note or a voice note with transcript, and offering a WhatsApp reply in one tap. Caller ID names the lead before the phone is answered. This is Android only and always will be — Apple does not expose the call log to third-party apps, and no CRM can work around that.

  MobileCall tracking

• Custody-only authentication

  ADR-0059. The separate vault passphrase was removed and there is now one login. The encryption was not removed — its custody moved, which is a materially different statement and one we spent several days sweeping the codebase and this website to state correctly. Every surface can now read every other surface’s records, which had not been true before.

  SecurityWebMobileHow access works

• Self-hosted over-the-air updates

  JavaScript fixes now reach installed phones without a reinstall, served from our own infrastructure rather than a third-party update service. The first live publish immediately found two bugs in the publish script itself, which is roughly what a first live publish is for.

  MobileAPI

• Live agent tracking and the field path

  Agent location on a firm map, with tracking stopping cleanly at both authentication boundaries rather than running on after sign-out. Site-visit check-in on location, quick actions from the map, and an offline queue that survives a cold start — which it had not been doing, because the queue was never rehydrated on boot.

  MobileSite visits

• React Native 0.81, Expo SDK 54, and real brand icons

  A full platform migration, plus the gold diamond mark on navy across the app icon, the Android adaptive icon, the splash screen and the monochrome notification icon. Before this the app shipped with placeholder art, which is a small thing that makes a product feel unfinished on a home screen.

  Mobile

• App Ops, fleet telemetry and a real download page

  An operations room showing what the deployed fleet is actually doing, and a download page that serves a genuine signed APK rather than a coming-soon message. Version drift between the filename and the app manifest was ended at the same time, because "which build is that" should not be a research question.

  WebAPIMobileDownload the app

A quiet month spent on the encryption cutover and on making deploys survive their own tooling.

• The encryption cutover, phase two

  The lead read path was rebuilt so that records written by any surface can be read by every other surface, with a verified backfill and the cutover gated behind a check rather than a hope. Before this, a record written on the phone could come back on the web as "(decryption failed)", which is the worst possible failure mode for a CRM.

  APISecurity

• Claims swept off the retired zero-knowledge language

  The developer documentation and several product surfaces still described a zero-knowledge model that the architecture had moved away from. They were rewritten to describe what actually runs: encryption at rest, no standing staff access, and an audit row on every access. Marketing copy that outlives its architecture is a liability, not an asset.

  MarketingSecurity

• A deploy script that waits for the build to finish

  A marketing deploy shipped a site with no CSS because the file copy raced the build process to completion. The fix is a script that waits for process exit rather than for a line of output, plus a guard that refuses to deploy if the static assets are missing. Written down here because it is the kind of failure a status page never mentions.

  Marketing

The first month. Everything below was built between the 9th and the 31st, which is also why some of it was rebuilt in August.

• The first public build

  The marketing site, the application shell and the pipeline. The lead capture form, the deal stages, the activity timeline and the encrypted record layer that everything else sits on. Nothing about this month was polished and all of it was real.

  WebAPIMarketing

• Attendance, leaves and payslips

  Employees, attendance with login hours, leave management, salary runs and payslips — the operational half of running a sales team, which most CRMs leave to a separate product and a separate subscription. Site staff attendance in particular is a real problem for firms running several project offices.

  WebAPIAttendance and payroll

• Lead sources, cohort retention and source ROI

  Which source produced bookings rather than which source produced volume, retention by cohort, and a lead-source by hour-of-day heatmap that turned out to be the most-used report in the demo workspace — because it tells a tele-calling desk when to call, which is a decision they make every single day.

  WebAPIReports and dashboards

• Reminders, the standup view and the automation engine

  A reminders API and a standup screen for the morning meeting, plus a lead-nurture rule engine so a follow-up can fire without anybody remembering it. The engine was later found writing a log row every minute for a state it could have computed, which grew one table to nine hundred thousand rows before anyone noticed.

  WebAPIAutomations and workflows

• Razorpay subscriptions with GST-correct invoicing

  Billing that produces an invoice an Indian accountant will accept: the correct GSTIN, the correct place of supply, and the tax stated rather than absorbed. Pricing has been restructured twice since, and this layer has held both times.

  APIPricing

• The super-admin portal, with TOTP

  The internal operator portal, behind two-factor authentication from its first commit, with an observability dashboard and route-level metrics. Staff access to any workspace has been auditable from the day the portal existed, which is the only sequence that makes the claim credible later.

  WebSecurity

• Voice-driven lead capture and voice-to-text

  Dictating a lead, a reminder or a visit note instead of typing it, including in Hindi. Built for the reality that an agent leaving a site office at 8pm will record a voice note and will not fill in a form.

  MobileAPI

• Multi-currency and FX snapshots — since narrowed

  Multi-currency display with exchange-rate snapshots and per-workspace currency preferences, built when the plan included a Gulf market. In August the site went India-only and rupee-only, and this work is dormant rather than deleted. It is listed because a changelog that quietly drops the things that did not pan out is not a record of anything.

  WebAPI