A two-sided market where families post care needs, caregivers apply, and organisations build a staffing bench — with verification visible at every step.
First commit 29 May 2026 · five-module platform in production 2 July 2026
The caregiver job board — filters for care type, child age and location, saved roles, and one-click apply.
What it does
Capabilities
Families post care roles with structured requirements: care type, schedule, pay rate, hours per week, start date and child age groups.
Caregivers filter by care type, child age, location and keyword, save listings, and apply in one click with an optional cover note and proposed rate.
A real application pipeline — Applied → Under Review → Shortlisted → Hired or Declined — visible to both sides, with duplicate applications blocked at the database.
Trust and safety filters narrow results to identity-verified and background-checked caregivers, with each badge explained inline rather than buried in a help page.
Threaded direct messaging between families, caregivers and organisations.
Nanny shares, co-hires, pods and micro-programs are modelled as first-class listing types, not free text.
How people use it
The journeys it was designed around
A parentFind someone for weekday afternoons
Posts a care role with structured fields — title, location, care type, schedule, pay rate, hours per week and start date — with required fields enforced in the browser and again on the server.
Saves it as a draft or publishes it immediately; drafts stay private until published.
Watches applications arrive on a dashboard of their own posted roles, each showing an applicant count and current status.
Opens the applicant list: avatar, name, professional headline, proposed rate and cover note per applicant, each card opening the full caregiver profile.
Moves an applicant through the pipeline, or opens a direct message thread without leaving the page.
A caregiverFind paid work that fits their week
Filters the job board by care type, maximum child age, location and free-text search; saves the roles worth returning to.
Opens a role to see the full description, requirements, pay, schedule and the family or organisation behind it.
Applies in one click, optionally attaching a cover note and a proposed rate.
Sees the button change to “Applied” — the system refuses a second application to the same role rather than silently creating a duplicate.
Tracks every application through Applied → Under Review → Shortlisted → Hired or Declined from a single applications view.
An organisationBuild a reliable staffing bench
Creates an organisation profile with locations and team members, then posts roles under the organisation rather than a personal account.
Filters candidates down to identity-verified and background-checked caregivers, and by the skills they have earned in the academy.
Invites specific caregivers to apply to a role directly, instead of waiting for inbound applications.
Manages staff invitations and roles through a members table with its own permission rules.
How it is built
Implementation and the rules real users find
Under the hood
Job posts, applications, invitations, saved listings and job skills are separate tables, each with row-level security scoped to the owning family, organisation or applicant.
Duplicate applications are prevented by a uniqueness constraint at the database, not by hiding the button — the UI state is a reflection of the constraint rather than a substitute for it.
Public caregiver and organisation profiles are served by SECURITY DEFINER functions that return a deliberately reduced record: no email, no phone number, last initial only.
Family listings carry their own child-facing detail — age groups, schedule, traits and what the family is open to — as related tables rather than a JSON blob, so they stay filterable.
Messaging is modelled as conversations with participants and messages, so a thread can hold a family, a caregiver and later an organisation without reshaping the data.
Verified badges shown in search are derived from the verification records, so a badge cannot be set by the profile it appears on.
The rules real users find
A deactivated account disappears from public search and is rejected at sign-in, but its historical applications stay intact for the families that received them.
Saved listings survive a role being unpublished — the caregiver sees that it closed rather than the entry silently vanishing.
Pay rate is optional on a post but a proposed rate is optional on an application, so either side can open the negotiation without either being forced to.
Safety prompts appear at the point of contact rather than in a terms page nobody reads.
The screens
Taken from the live product
Click any shot to enlarge.
The filter sidebar: care type, child age, location and trust criteria.A role in full — requirements, pay, schedule and a direct route to message the family.After applying, the action becomes a status. Re-applying is blocked at the database.The parent’s applicant list — headline, proposed rate and cover note per candidate.A caregiver profile drawer opened from search, without losing the result set.Every badge explains what it actually certifies, inline.Safety guidance surfaced at the moment of first contact.The parent’s own posted roles, with applicant counts and status.
The rest of the platform
All 5 modules
These were built on one schema and one permission model, which is the only reason all 5 of them could ship together.
SigmaticAI is led by Ketan Khamgaonkar — an IIT Roorkee M.Tech who went on to PhD research at IIT Bombay before spending four years building AI automation, agentic systems and full web and mobile products. On every project you talk to the person writing the code.
No pitch deck. Tell us what you are trying to ship and we will tell you the fastest honest path to live — including if that path is smaller than you thought.