About the Client
| Client | Bayleys Real Estate |
| Industry | Commercial & residential property | sales · valuation · property management |
| Region | New Zealand | one of NZ’s largest full-service real estate companies |
| Application | CVE — Commercial Valuation Evidence | internal property evidence platform |
| Legacy | Microsoft Access database → migrated to Aurora PostgreSQL on AWS |
| Delivered by | Peritos Solutions | Oct 2023 – Dec 2023 |
Bayleys is one of New Zealand’s leading full-service real estate companies, operating across commercial, industrial, residential and rural property. Their internal CVE application is used by valuers to record, search, and report on commercial sales and rental evidence across the New Zealand market.
Project Background
Bayleys’ existing Commercial Valuation Evidence system ran on a legacy Microsoft Access database — a standalone, desktop-bound solution with no cloud access, no modern search capability, and no ability to scale to a growing user base. The requirement was to migrate the entire application to a cloud-native platform that could be accessed from any device, support role-based access aligned to Bayleys’ existing Azure AD identity, and provide a significantly improved user experience for valuers entering and searching property evidence.
Peritos Solutions was engaged to design, build, and deploy the full application on AWS — from architecture design and Access database migration through to a React.js frontend, serverless C# API layer, Aurora PostgreSQL database, and production deployment — in under two months.
Project Timelines
| Phase | Period | Key Activities | Status |
| Phase A | Oct 2023 | Requirement gathering, AS IS / TO BE flows, business architecture, application design, AWS account structure setup (Dev/Test/Prod OUs) | Done |
| Phase B | Oct – Nov 2023 | AWS infrastructure setup, React.js frontend, C# Lambda APIs, AWS Cognito + Azure AD SSO, property search, sales entry, rental entry, photo/attachment upload, CI/CD pipelines, unit testing | Done |
| Phase C | Nov – Dec 2023 | Word/Excel export, Google Maps radius search, audit logs, email report delivery, advanced search enhancements | Done |
| Phase D | Dec 2023 | Access DB data migration to Aurora PostgreSQL, UAT, bug fixing, production deployment, documentation & handover | Done |
| Hypercare | Dec 2023 | 1-month free hypercare post go-live, then transition to support contract | Done |
Results & Impact
Observability & Visibility
Assessment Report
Phase A delivered a structured assessment before any build commenced:
- Risk & Gap Analysis — AS IS Access database reviewed, TO BE cloud architecture designed, data migration approach confirmed, and AWS account structure (Dev/Test/Prod organisation units) set up before development started
- Customised Assessment Report — AWS Well Architected Framework assessment completed across all five pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation), with adherence built into the architecture from day one
- Pricing validated — full AWS pricing model confirmed at USD $124.22/month (Asia Pacific Sydney) before infrastructure was provisioned
Cloud Formation
Serverless AWS Architecture
The entire application was built on a consumption-based serverless model:
- AWS Lambda (C#) — all backend APIs run serverless with automatic scaling, zero server management, and 99.95% SLA
- Aurora Serverless PostgreSQL — database scales automatically with demand, 99.99% SLA, deployed in a private subnet with no public internet access
- AWS Amplify — React.js frontend deployed on a managed CloudFront distribution with built-in level 7 security — no additional CDN or WAF configuration required for the frontend
- CloudFormation IaC — all three environments (Dev/Test/Prod) provisioned from identical infrastructure-as-code scripts, ensuring full environment parity
Scope & Requirements
Phase A — Requirements & Architecture
- AS IS and TO BE process flows documented for sales and rental evidence workflows
- AWS account structure designed — separate Dev, Test, and Prod accounts under an Organisation Unit hierarchy
- Application architecture designed — serverless, multi-layer (Presentation · Business Services · Data Access)
- AWS Well Architected Framework review completed across all 5 pillars
- AWS pricing model confirmed — USD $124.22/month
Phase B — Core Application
- AWS infrastructure setup — VPC, private subnets, CloudFormation scripts, CI/CD pipelines
- User authentication — AWS Cognito with Azure AD as identity provider; JWT token validation on every Lambda; admin/user role assignment from AD groups
- Home screen and navigation — role-based dashboard
- Commercial Valuation Evidence (CVE) module — full sales evidence entry with NZ address restriction
- Property search — by type, category, subcategory, location, date range, price, building area, tenure, zoning, keyword
- Rental Assessment module — rental entry with auto-calculated annual rental (area × contract rate), lease terms, occupancy details
- Photo and document attachment — upload, download, and delete for both sales and rental records; stored in S3
- Sales and rental evidence report — combined report generation
- AWS deployment — Lambda, Aurora, Amplify, API Gateway, WAF, S3, KMS, Secrets Manager, CloudWatch
Phase C — Additional Features
- Word and Excel export of property evidence reports
- Google Maps radius search — restrict property search to X km radius of a searched NZ address
- Audit logs — logging of all data download and export events
- Email report delivery — send evidence reports via SNS/SQS email integration
- Advanced search enhancements — comma formatting on numeric fields, improved address suburb search
Phase D — Data Migration & Production
- Full data migration from Microsoft Access database to Aurora PostgreSQL
- UAT, bug fixing (5% effort allocation), production deployment
- Documentation and handover
- 1-month hypercare support post go-live
Implementation
Serverless Architecture
The backend was built entirely on AWS Lambda using C#, invoked via Amazon API Gateway. This eliminated server management entirely — Lambda scales automatically to handle any volume of concurrent requests, and the consumption-based pricing model means Bayleys pays only for actual usage. At 50,000 Lambda invocations per month, the Lambda cost is effectively zero under AWS’s free tier thresholds.
Authentication — Azure AD + AWS Cognito
Bayleys users authenticate using their existing Bayleys corporate Azure AD credentials. AWS Cognito is configured with Azure AD as the federated identity provider — users click ‘Sign in with Bayleys account’, are redirected to Azure AD for authentication, and returned to the CVE app with a JWT token. Admin role assignment is handled via Azure AD group membership, surfaced in the JWT claim and enforced on every Lambda endpoint.
Property Search & Google Maps Integration
The property search module allows Bayleys valuers to search commercial sales and rental evidence by property type, category, subcategory, location, date, price, building area, tenure, and keyword. NZ address lookup is powered by the Google Maps Places API with results restricted to New Zealand addresses only. The radius search feature allows valuers to find all comparable evidence within a defined kilometre radius of any NZ address — critical for commercial valuation work.
Data Model & Migration
The existing Microsoft Access database was analysed, mapped to a normalised PostgreSQL schema, and migrated to Amazon Aurora Serverless. Aurora’s serverless configuration means the database scales its capacity units automatically based on load — dropping to near-zero cost during idle periods and scaling up for peak search and reporting activity. The database is deployed in a private subnet with no public internet access; Lambda functions access it over the private network only.
Security Architecture
All API endpoints are protected by AWS WAF with AWS managed rule groups covering common web exploits, SQL injection, and bot traffic. AWS Shield Standard provides DDoS protection at the network layer. All sensitive configuration (database connection strings, API keys, third-party credentials) is stored in AWS Secrets Manager in encrypted format. Data at rest in Aurora and S3 is encrypted using AWS KMS. All data in transit is secured via HTTPS/TLS.

Technology & Architecture
| Frontend | React.js | AWS Amplify | responsive | Chrome · Edge · Firefox · Safari |
| Backend | C# (.NET) | AWS Lambda (serverless) | AWS API Gateway | event-driven architecture |
| Database | Amazon Aurora Serverless (PostgreSQL) | 99.99% SLA | auto-scaling | private subnet |
| Auth | AWS Cognito | Azure AD as identity provider | JWT tokens | role-based access (admin / user) |
| Storage | Amazon S3 | PDFs · photos · attachments | private endpoint access from Lambda | KMS encryption |
| Networking | AWS VPC | private subnets for Lambda & Aurora | AWS WAF on API Gateway | AWS Shield Standard |
| Security | AWS WAF (managed rule groups) | AWS Shield Standard | AWS KMS | AWS Secrets Manager | SSL/TLS |
| Notifications | Amazon SNS | Amazon SQS | email delivery for property reports |
| Monitoring | Amazon CloudWatch | AWS CloudTrail | alert & monitoring dashboards |
| DevOps | AWS CloudFormation (IaC) | CI/CD pipelines | Dev · Test · Prod environment parity |
| Integrations | Google Maps API (NZ address lookup · radius search) | Azure AD SSO | Word/Excel/PDF export |
| Region | Asia Pacific — Sydney | monthly AWS cost: USD $124.22 | 12-month total: USD $1,490.69 |
Architecture Overview
A high level architecture diagram as below


Challenges
Access Database Migration to Aurora PostgreSQL
The legacy Microsoft Access database had an unstructured schema built over many years of ad hoc property data entry. Peritos mapped the full Access data model to a normalised PostgreSQL schema before migration, handled data type conversions, and validated migrated data record-by-record against the source before go-live.
Azure AD Federated Identity via AWS Cognito
Integrating Bayleys’ corporate Azure AD as the identity provider for an AWS-native application required careful configuration of OIDC federation in Cognito, JWT claim mapping for admin role detection, and testing across all authentication edge cases — including token expiry, re-authentication, and admin privilege escalation via group membership.
NZ-Only Address Restriction
Google Maps Places API returns global results by default. Enforcing NZ-only address lookup required both frontend component configuration (restricting the Places autocomplete to NZ) and backend validation on address submission — ensuring no non-NZ property records could be created through direct API calls.
Complex Valuation Analysis Fields
The sales evidence entry form includes specialist commercial valuation fields — Building Rate ($/psm), Equivalent Market Yield (%), IRR (%), WALT (years to 2dp), Vacancy (%) — each with specific unit formatting requirements and conditional display rules (e.g. subcategory only active for Commercial Office and Commercial Retail). Getting the field logic right required close collaboration with Bayleys valuers through multiple UAT cycles.
Under Two Months End-to-End
Delivering a fully serverless custom application — including data migration, three AWS environments, CI/CD pipelines, Azure AD integration, Google Maps integration, and report export — in under two months required strict parallel workstreaming across infrastructure setup, backend development, frontend development, and data migration, with daily sprint cycles and rapid UAT feedback turnarounds.
Key Benefits
- Fully serverless — zero server management, automatic scaling, consumption-based pricing at USD $124/month for a full commercial property evidence platform
- Single sign-on — Bayleys staff use their existing corporate Azure AD credentials with no new password or account required
- Cloud-native from day one — built following the AWS Well Architected Framework across all 5 pillars, with IaC (CloudFormation) and CI/CD pipelines ensuring repeatable, reliable deployments
- Access database retired — legacy desktop-only, single-user Access database replaced by a scalable multi-user cloud application accessible from any device and browser
- Google Maps radius search — valuers can find comparable evidence within any km radius of any NZ address, directly inside the application without external tools
- 99.99% database SLA — Aurora Serverless PostgreSQL delivers enterprise-grade availability with automatic failover and no database administration overhead
- Complete audit trail — CloudWatch logging, CloudTrail, and application-level audit logs capture all data access and export activity
Post-Launch Support
Hypercare Period
A 1-month free hypercare period was included from the go-live date. Peritos monitored CloudWatch metrics, resolved all post-launch issues, and provided guidance on Aurora capacity tuning and Lambda concurrency configuration. All Phase B UAT test scenarios (45+ test cases across sales entry, rental entry, and search) were confirmed passed before the hypercare period commenced, with only 3 bugs raised and resolved during testing.
A support contract proposal was prepared for ongoing AMC support following the hypercare period, covering Lambda, Aurora, Amplify, and application-level support.
About the Client
| Client | HR Mind — a Profiler Group Company |
| Industry | Global Recruitment & Workforce Management |
| Sectors | Industrial · E-commerce · Infrastructure & EPC · Renewable Energy · Automotive · IT · Healthcare · FMCG |
| Experience | 9 years | global leader in recruitment and workforce management strategies |
| Website | hrmind.com |
| Delivered by | Peritos Solutions |
HR Mind is a global recruitment and resourcing company with 9 years of industry experience, serving clients across Industrial, E-commerce, Infrastructure & EPC, Renewable Energy, Automotive, IT, Healthcare, FMCG, and Consumer Durables sectors. As a Profiler Group company, HR Mind brings enterprise-grade workforce management strategies to clients worldwide.
Project Background
HR Mind required a new website that reflected their standing as a global recruitment leader — professional, fast, and capable of generating qualified leads from both candidates and employers across their 8+ industry verticals. Their previous web presence did not represent their brand effectively, lacked CRM integration, and was not optimised for search engine visibility.
Peritos Solutions was engaged to deliver the complete project end-to-end: brand-aligned UI/UX design, WordPress development, CRM lead generation integration, and production hosting on AWS — all within a compressed one-month timeline. The requirement was a site that would rank on Google, load fast globally, capture leads automatically, and stay online reliably.
Project Timelines
| Phase | Week | Key Activities | Status |
| Phase 1 | Week 1 | Discovery & planning — requirements, sitemap, wireframes, AWS architecture design, domain & DNS setup (Route 53) | Done |
| Phase 2 | Week 1–2 | UI/UX design — brand-aligned page designs, mobile-responsive layouts, CRM lead form wireframes reviewed & signed off | Done |
| Phase 3 | Week 2–3 | Development — WordPress/CMS build, all pages coded, CRM integration (HubSpot/Zoho), contact & lead capture forms live | Done |
| Phase 4 | Week 3 | AWS infrastructure setup — EC2, S3, RDS, CloudFront CDN, ACM SSL, IAM roles, AWS Backup, CloudWatch monitoring configured | Done |
| Phase 5 | Week 3–4 | SEO implementation — on-page SEO, meta tags, schema markup, XML sitemap, robots.txt, Google Search Console & Analytics setup | Done |
| Phase 6 | Week 4 | QA, performance testing, Core Web Vitals validation, UAT sign-off, DNS cutover, go-live & 2-week hypercare support | Done |
Scope & Requirements
Website Design & Development
- Brand-aligned UI/UX design — mobile-first, responsive layouts across all pages
- WordPress CMS build — enabling HR Mind’s team to manage content independently post-launch
- Pages: Home, About, Industries (8 verticals), Services, Careers, Contact
- Lead capture forms — candidate registration, employer enquiry, and job submission forms
- Performance optimisation — image compression, lazy loading, minified CSS/JS, Core Web Vitals compliance
CRM Lead Generation Integration
- CRM integration (HubSpot / Zoho) — all form submissions routed directly to CRM pipeline
- Lead segmentation — candidate vs. employer leads tagged and routed to separate CRM pipelines
- Automated email notifications — internal team alerted on new lead submission
- UTM parameter tracking — all CRM leads tagged with source, medium, and campaign for ROI reporting
SEO Optimisation
- On-page SEO — title tags, meta descriptions, H1/H2 structure, keyword-optimised copy for all pages
- Technical SEO — XML sitemap, robots.txt, canonical tags, structured data (schema markup)
- Google Search Console and GA4 setup — tracking, indexing, and performance monitoring from day one
- Core Web Vitals — LCP, FID, and CLS all passing green on both mobile and desktop at launch
AWS Hosting & Infrastructure
- Amazon EC2 (t3.medium) with Auto Scaling Group — scales up automatically under traffic spikes
- Application Load Balancer — distributes traffic across EC2 instances with health checks
- Amazon RDS MySQL Multi-AZ — production database with automatic failover and daily snapshots
- Amazon S3 — static asset storage, media library, and backup storage
- Amazon CloudFront CDN — global content delivery from 400+ edge locations
- Amazon Route 53 — DNS management with latency-based routing
- AWS ACM — free SSL/TLS certificate provisioned and auto-renewed
- AWS WAF — web application firewall protecting against OWASP Top 10 threats
- AWS Backup — automated daily backups, 30-day retention, cross-region recovery
- Amazon CloudWatch + SNS — uptime monitoring, CPU/memory alarms, email alerts
Implementation
Week 1 — Discovery & Architecture
Peritos ran a rapid discovery sprint covering HR Mind’s brand guidelines, target audience (candidates and employers across 8 sectors), CRM system, and hosting requirements. The AWS architecture was designed and presented for sign-off — service selection justified against traffic profile, budget, and availability targets. Domain and DNS were migrated to Route 53 immediately to begin SSL provisioning via ACM.
Week 2 — Design & Development
UI/UX designs were produced in Figma, reviewed, and signed off by HR Mind within 3 business days. WordPress development commenced in parallel — custom theme built from approved designs, all pages developed, and CRM lead capture forms integrated and tested end-to-end. Mobile responsiveness and cross-browser compatibility validated across Chrome, Safari, Firefox, and Edge.
Week 3 — AWS Infrastructure
The full AWS production stack was provisioned: EC2 instance launched and configured, RDS MySQL Multi-AZ database deployed, S3 bucket configured for media and backups, CloudFront distribution created with custom domain and ACM SSL, WAF rules applied, IAM roles locked down to least-privilege, and AWS Backup policies set. CloudWatch dashboards and SNS alarms configured for uptime, error rate, and resource utilisation.
Week 4 — SEO, QA & Go-Live
On-page SEO implemented across all pages — meta tags, schema markup, XML sitemap submitted to Google Search Console, GA4 tracking verified. Full QA pass covering functional testing, form submission flows, CRM lead routing, load testing, and Core Web Vitals audit. DNS cutover executed during a low-traffic window, SSL confirmed live, and the site went live within the agreed timeline.
Application screenshots placeholder — insert homepage, industry pages, lead capture form, CRM pipeline, and AWS console views here.

Results & Impact
Observability & Visibility
Assessment Report
Before development commenced, Peritos conducted a rapid discovery and assessment covering:
- Risk & Gap Analysis — reviewed HR Mind’s existing web presence, identified SEO gaps, CRM integration requirements, and hosting constraints before any design or build work began
- Customised Assessment Report — delivered a scoped architecture proposal covering AWS service selection, CRM integration approach, SEO strategy, and go-live timeline within the first week
- AWS architecture confirmed — service selection (EC2, RDS Multi-AZ, CloudFront, Route 53, WAF, Backup) validated against HR Mind’s traffic profile and availability requirements before infrastructure provisioning
Cloud Formation
AWS Infrastructure
The complete AWS stack was provisioned, configured, and hardened within week 3 of the engagement:
- Multi-AZ RDS deployment ensures database availability with automatic failover — zero downtime for planned maintenance
- CloudFront CDN delivers static assets from 400+ global edge locations — reducing load times by 3x for international candidates and employers
- AWS Backup configured with daily automated snapshots, 30-day retention, and cross-region backup for full disaster recovery coverage
- AWS WAF protects against common web exploits, SQL injection, and DDoS — all traffic inspected before reaching the application layer
Technology & Architecture
| Compute | Amazon EC2 (t3.medium) | Auto Scaling Group | Application Load Balancer (ALB) |
| Storage | Amazon S3 | static assets, media, backups | S3 Versioning enabled |
| Database | Amazon RDS (MySQL) | Multi-AZ deployment | automated snapshots |
| CDN & DNS | Amazon CloudFront | global edge caching | Amazon Route 53 | SSL via AWS ACM |
| Security | AWS IAM | least-privilege roles | AWS WAF | Security Groups | ACM SSL/TLS |
| Backup | AWS Backup | automated daily snapshots | 30-day retention | cross-region backup |
| Monitoring | Amazon CloudWatch | uptime alarms | CPU & memory metrics | SNS email alerts |
| CMS / Frontend | WordPress | custom theme | mobile-responsive | Core Web Vitals optimised |
| CRM Integration | HubSpot / Zoho CRM | lead capture forms | contact routing | pipeline automation |
| SEO | Yoast SEO | XML sitemap | schema markup | Google Search Console | GA4 |
Architecture Overview

Challenges
Compressed One-Month Timeline
Design, development, CRM integration, AWS setup, SEO, and go-live all within four weeks required strict parallel workstreaming. Peritos ran design and development concurrently, began AWS provisioning in week 2 (before development was complete), and ran SEO implementation in parallel with QA — compressing what is typically a 2–3 month engagement into four weeks without cutting scope.
Multi-Sector Content Architecture
HR Mind operates across 8 industry verticals — each requiring distinct messaging, keywords, and page structure for SEO effectiveness while maintaining a consistent brand. Peritos designed a templated industry page structure that HR Mind’s team can replicate for new verticals independently, without developer involvement.
CRM Lead Routing Logic
Candidate and employer leads required different routing rules, pipeline stages, and internal notification recipients within the CRM. Peritos mapped the full lead lifecycle before development, built conditional routing logic into the form integration layer, and tested all paths end-to-end before go-live.
DNS Cutover with Zero Downtime
Migrating DNS from the previous hosting provider to Route 53 required careful TTL management and timing to avoid any window of downtime. Peritos lowered TTLs 48 hours before cutover, executed the switch during a low-traffic period, and had the old origin on standby for immediate rollback — the cutover completed with no downtime recorded.
Key Benefits
- Live in under 1 month — full design, build, AWS hosting, CRM integration, and SEO delivered end-to-end in under 4 weeks
- Automated lead generation — every candidate and employer enquiry flows directly into the CRM pipeline with zero manual handling
- Global performance — CloudFront CDN ensures fast load times for HR Mind’s international audience across all 8 industry sectors
- Enterprise-grade security — AWS WAF, IAM least-privilege, ACM SSL, and Security Groups protect the site and its data at every layer
- Fully recoverable — AWS Backup with 30-day retention and cross-region recovery ensures HR Mind’s site and data can be restored from any failure scenario
- SEO-ready from day one — Core Web Vitals passing, Google Search Console live, and structured data in place before the first visitor arrived
- Self-manageable CMS — WordPress enables HR Mind’s team to update content, add jobs, and manage pages independently without developer support
Post-Launch Support
Hypercare Period
A 2-week hypercare period was included post go-live. During this period Peritos monitored CloudWatch metrics daily, resolved any content or performance issues identified by HR Mind’s team, and made minor CRM routing adjustments based on real lead data. All CloudWatch alarms, backup policies, and WAF rules were reviewed and tuned before formal handover.
Full handover documentation covering AWS architecture, WordPress admin guide, CRM lead routing logic, and DNS management was delivered to HR Mind at the close of the hypercare period.
About Ektos Health
Ektos Health was built by Peritos Solutions in response to a clear gap in the Indian healthcare market: hospitals and diagnostic centres were running on fragmented systems — paper-based appointment registers, disconnected lab software, manually typed prescriptions, and spreadsheet billing. The result was errors, delays, compliance risk, and frustrated staff.
The vision was to build a single, cloud-based HMIS that any hospital — from a small diagnostic centre to a multi-specialty hospital — could deploy without heavy IT infrastructure, get up and running quickly, and be confident it met India’s digital health standards from day one.
Ektos Health is proudly developed by Peritos Solutions and is available at ektos-health.com. It is deployed for diagnostic centres, polyclinics, and hospitals across India.
The Problem
- Appointment booking managed on paper or basic spreadsheets — no real-time visibility of doctor availability or patient queue
- Lab test requests, sample tracking, and report delivery disconnected from patient records — requiring manual re-entry
- Prescription generation required doctors to type everything manually — time-consuming, error-prone, and inconsistent
- No intelligent support for diagnosis — doctors working without access to the patient’s full history and previous diagnoses at the point of consultation
- IPD admission and bed management done manually — no real-time bed availability visibility
- Billing disconnected from clinical services — charges for lab tests, consultations, and procedures reconciled separately
- No compliance infrastructure for ABDM or NABH — hospitals at risk of failing accreditation requirements
- Patient health records not linked to national health IDs (ABHA/Aadhaar) — no interoperability with India’s digital health ecosystem
Scope & Feature List
|
Module 1 — Appointment Booking & Management |
|
A centralized, real-time appointment management system for walk-in and online bookings:
|
|
Module 2 — Patient Management |
|
Complete end-to-end patient record management — from first registration to ongoing care:
|
|
Module 3 — Laboratory Management (Diagnostic Centre) |
|
End-to-end lab workflow management — from test assignment to report delivery — purpose-built for diagnostic centres:
|
|
Module 4 — AI Prescription Generation & Clinical Intelligence |
|
The AI layer is the most powerful differentiator in Ektos Health — enabling doctors to generate accurate, formatted prescriptions in under a minute using voice or text, with AI-assisted diagnosis support: Voice-to-Text Prescription Dictation
AI-Generated Diagnosis Suggestions
AI Prescription PDF Generation
|
|
Module 5 — Admission & Discharge (IPD) |
|
Full inpatient lifecycle management — from bed allocation on admission to discharge summary generation:
|
|
Module 6 — Billing Management |
|
Integrated, transparent billing across all hospital services — from OPD consultations to lab tests and inpatient stays:
|
|
Module 7 — Settings, Master Data & System Configuration |
|
Full control over how Ektos Health operates within your institution:
|
ABDM & NABH Compliance
Ektos Health is built from the ground up to meet India’s national digital health standards — not as an afterthought, but as a core architectural requirement:
|
ABDM Compliance |
Full integration with Ayushman Bharat Digital Mission — ABHA creation, verification, and health record linkage built into appointment, lab, and prescription workflows |
|
ABHA Integration |
Patients can create a new ABHA (Ayushman Bharat Health Account) or link an existing one at registration — enabling secure nationwide health record interoperability |
|
Aadhaar Verification |
Aadhaar-based patient identity verification supported at registration and appointment booking |
|
Digital Prescriptions |
AI-generated prescription PDFs comply with ABDM digital prescription standards — shareable via ABHA |
|
NABH Standards |
Workflow design, documentation requirements, consent management, and audit trails align with NABH accreditation criteria |
|
Audit Trails |
All clinical and administrative actions logged with user, timestamp, and action type — supporting NABH audit requirements |
|
Data Security |
Patient health data encrypted at rest and in transit — role-based access prevents unauthorised data exposure |
|
Compliance Readiness |
90% compliance readiness score across ABDM/NABH requirements — hospitals go live already meeting accreditation benchmarks |
Technology & Architecture
Ektos Health is a cloud-native application built on modern web technologies, deployed on scalable cloud infrastructure:
|
Frontend |
React.js — fast, responsive, mobile-compatible web interface — works on desktop, tablet, and mobile without a separate app |
|
Backend |
Node.js / Python REST APIs — microservice architecture for each module (appointments, lab, billing, AI) |
|
Cloud |
Cloud-hosted — scalable, high-availability infrastructure with 24/7 uptime monitoring |
|
Database |
Secure relational database with full patient record history, audit logs, and real-time updates |
|
AI Engine |
GPT-4 integration for diagnosis suggestions and prescription generation — custom prompt engineering for clinical context |
|
Voice-to-Text |
Speech recognition API with medical vocabulary training — dictation converted to structured prescription text |
|
PDF Engine |
Automated prescription and lab report PDF generation — templated, branded, and configurable per department |
|
ABDM API |
Official ABDM API integration — ABHA creation, verification, and health record exchange |
|
Notifications |
SMS and email notification engine — appointment reminders, lab result alerts, billing confirmations |
|
Security |
Role-based access control, encrypted data transmission, session management, and full audit logging |
AI Features — How They Work
|
AI Feature |
How It Works |
Clinical Benefit |
|
Voice-to-Text Prescription |
Doctor speaks the prescription aloud. Speech recognition converts dictation to structured text — drug names, dosages, instructions — in real time. Doctor reviews and confirms before saving. |
Consultation time reduced significantly. Doctor maintains eye contact with patient rather than typing. Reduces transcription errors. |
|
AI Diagnosis Suggestion |
Doctor enters chief complaint and clinical notes. AI analyses these against the patient’s stored diagnosis history and symptom patterns to suggest probable diagnoses ranked by likelihood. |
Supports junior doctors with differential diagnosis. Reduces diagnostic oversight. Highlights conditions to rule out. Improves clinical decision quality. |
|
AI Prescription PDF |
Once diagnosis and treatment are confirmed, the system auto-generates a formatted, branded prescription PDF including patient details, diagnosis, medications with dosage and frequency, and follow-up date. |
Professional, legible, legally compliant prescriptions every time. Stored against patient record. Shareable via ABHA. No formatting overhead for doctor. |
|
Previous Diagnosis Context |
AI accesses the patient’s full longitudinal history — all previous diagnoses, medications, allergies, and test results — as context when generating suggestions for the current visit. |
Prevents prescribing contraindicated medications. Highlights recurring conditions. Improves continuity of care across multiple visits and doctors. |
Implementation Approach
Ektos Health is deployed as a cloud SaaS product. New hospitals and diagnostic centres can be onboarded and live within days:
|
Day 1–2 — Setup |
Hospital profile, branding, departments, doctors, and billing items configured in Master Data and Settings. User roles and access levels assigned. |
|
Day 2–3 — Integration |
ABDM/ABHA API connection configured. SMS/email notification templates set up. Diagnostic machine connectivity tested where applicable. |
|
Day 3–4 — Data Entry |
Existing patient records migrated or entered. Lab test catalogue configured. Room and bed categories set up for IPD centres. |
|
Day 4–5 — Training |
Staff training on appointment, lab, billing, and prescription workflows. Doctors trained on voice-to-text and AI diagnosis features. |
|
Day 5 — Go-Live |
Live patient appointments and consultations begin. Peritos Solutions provides hypercare support for the first two weeks post-launch. |
|
Ongoing |
24/7 cloud support. Feature updates deployed automatically. AI model improves with usage. ABDM regulatory updates applied centrally. |
Client Testimonials
|
“Ektos Health has significantly streamlined our operations and improved efficiency across our healthcare workflows. The platform is intuitive, reliable, and backed by a highly responsive team at Peritos Solutions.” — Akanksha Niranjan, Director, Ekanshi Solutions, Lucknow |
|
“The platform has simplified our day-to-day clinic management, from patient records to reporting. It has reduced manual work and improved overall efficiency. The support team is proactive and always available when needed.” — Dr. Ramnath Mishra, Clinic, Bhubaneswar |
|
“Ektos Health has transformed how we manage patient records and hospital operations. The system is easy to use, secure, and provides quick access to critical information, enabling us to deliver better patient care.” — Dr. Anil Chowdhary, Lal Kothi Hospital, Jaipur |
Key Benefits
- Single integrated platform replacing 4–6 disconnected systems — appointments, lab, prescriptions, billing, IPD, and patient records all in one
- AI-powered prescription generation reduces doctor consultation time by 40–60% — voice dictation eliminates manual typing
- AI diagnosis suggestions based on chief complaint and full patient history — improves clinical decision quality, especially for junior doctors
- Automated PDF prescription and lab report generation — professional, branded, legally compliant output every time
- Real-time bed management and IPD visibility — no more manual bed registers or phone calls to check availability
- Full ABDM compliance from day one — ABHA integration, digital prescriptions, and interoperability with India’s national health ecosystem
- NABH-aligned workflows, consent management, and audit trails — reduces accreditation preparation effort significantly
- Cloud-based deployment — no on-premise servers required, accessible from any device, 24/7 uptime
- Configurable without IT support — branding, templates, user roles, and settings managed by hospital administrators
- Scalable from a single diagnostic centre to a multi-specialty hospital — same platform, different configuration
Ready to Transform Your Hospital’s Operations?
Book a free demo of Ektos Health HMIS — and see AI prescription generation, voice-to-text, lab management, and ABDM compliance in action. Deployed and live within days.
info@ektos-health.com | ektos-health.com | Peritos Solutions | www.peritossolutions.com
About the Client
Bayleys Real Estate is one of New Zealand’s largest and most recognised real estate agencies, operating across residential, commercial, rural, and property management services throughout New Zealand and Australia (including McGrath Real Estate). With over 150 property management agents generating 1,800–2,000 rental appraisals per month, the volume and complexity of documentation demanded a step-change in how the business operated.
The leadership team — including the National Director and Financial Director — identified AI-driven automation as the strategic priority, with a clear mandate: reduce time spent on repetitive documentation tasks, improve consistency and accuracy, and free agents to focus on client relationships.
The Problem
Each rental appraisal traditionally required an agent to manually complete market analysis, write a property description, cross-reference compliance requirements, and produce a formatted report — a process taking 30 to 45 minutes per appraisal. At an average cost of NZD $50 per agent-hour, this represented a significant and measurable drag on productivity.
With 1,800 to 2,000 appraisals generated per month — and a target of 60,000 to 67,000 per year — the business needed automation, not incremental improvement. Key pain points included:
- Inconsistent quality and formatting of appraisals across regions and agents
- No centralised, AI-assisted way to access tenancy legislation, tribunal case law, or market data
- Agents frequently leaving the platform to search external sites for comparable properties or school zone information
- Manual population of agent profiles, property features, and branding on every report
Solution Overview
Peritos Solutions designed and built a two-module platform hosted on Microsoft Azure, integrating with Bayleys’ existing technology ecosystem including Office 365, CoreLogic, and the Bayleys property API.
|
Part 1 — Automated Appraisal Engine |
|
The appraisal engine automates the end-to-end production of a professional, branded rental appraisal report. A property manager enters or confirms a property address and the system handles the rest:
|
|
Part 1 — EMV (Estimated Market Value) Engine |
|
The EMV engine is the technical centrepiece of the appraisal platform. Peritos evaluated multiple modelling approaches and selected a Random Forest Regression model, trained on data from the Bayleys Data Lake, as the optimal fit for rental valuation. The model evolved through three refinement stages:
Key technical components of the EMV model include:
|
|
Part 2 — AskKen AI Chatbot |
|
AskKen AI is a purpose-built real estate intelligence assistant, powered by OpenAI GPT-4O with a custom AI engine layered on top to control output quality and data sources. It is accessible via mobile and desktop and requires no training to use. The architecture uses Retrieval-Augmented Generation (RAG) to ground the LLM’s responses in Bayleys‘ proprietary and controlled data sources rather than the open internet:
AskKen AI is capable of handling queries across legislation and compliance, comparable market analysis, tenancy tribunal precedents, suburb and school zone research, rental market reports, maintenance cost estimates, yield calculations, and more. |
Technical Architecture
|
Cloud Platform |
Microsoft Azure — cloud-native, scalable infrastructure |
|
AI / LLM Core |
OpenAI GPT-4O with supervised fine-tuning and custom prompt engineering |
|
Valuation Model |
Random Forest Regression — bootstrap aggregation, geometric mean, Pearson R correlation weighting |
|
RAG Layer |
Vector store indexing of proprietary legal, market, and operational documents — real-time retrieval at query time |
|
Data Lake |
Bayleys proprietary property data, appraisal history, and manually entered new-build data |
|
Integrations |
CoreLogic API (property attributes), Bayleys API (listing images), Office 365 SSO (user profiles) |
|
AI Copywriting |
Sentiment-analysis-trained model on thousands of historical appraisals — generates descriptions matching Bayleys tone |
|
Output |
Professionally formatted, branded PDF appraisal report with agent profile, property image, EMV, description, and disclaimer |
|
Platforms Supported |
Web (desktop, mobile, tablet) — zero-training, no-manuals design philosophy |
|
Markets |
New Zealand (primary) — extensible to Australia (McGrath Real Estate) |
|
Security |
Internal vs external data segregation; only version-controlled approved data ingested into AI; external web search disabled by default |
Key Challenges & Solutions
|
First AI project under scrutiny |
As Bayleys‘ inaugural AI initiative, the project carried high visibility. Peritos delivered on time, within budget, and with quantifiable ROI — establishing the blueprint for future AI projects across the business. |
|
EMV accuracy |
Initial models had ±15% error. Through iterative refinement — geometric mean aggregation, Pearson R suburb correlation, and full feature weighting — accuracy was driven to ±3% nationwide, matching experienced agent assessments. |
|
No-training UX requirement |
The platform was designed to require zero manuals or training, following the design philosophy that a good product is intuitive regardless of technical experience. The interface works seamlessly across mobile, desktop, and tablet. |
|
Data gaps for new properties |
Off-plan and newly built properties often lack data in CoreLogic or the Bayleys API. A manual entry flow was built to capture this information, feeding it directly into the Data Lake to improve future model accuracy. |
|
Cross-market compatibility |
The platform was architected to support both New Zealand and Australian markets from a single codebase, with regional disclaimer management configurable by administrators. |
|
RAG grounding vs hallucination |
Rather than relying on the open internet, all AI responses are grounded in controlled, indexed proprietary documents. A guardrails layer strips unsupported assertions before they reach the user. |
Financial Impact
|
Appraisal time reduction |
From 30–45 minutes per appraisal to under 1 minute — saving approximately 40 minutes per appraisal |
|
Appraisal volume |
1,800–2,000 appraisals per month (60,000–67,000 annually) |
|
Saving per appraisal |
NZD $33.33 per appraisal (based on NZD $50/hr agent cost) |
|
Annual appraisal saving |
NZD $720,000–$800,000 per year from appraisal automation alone |
|
AskKen AI research saving |
10 hours of manual research saved per agent per month × 150 agents × NZD $50/hr = NZD $75,000/month |
|
Annual AskKen saving |
NZD $900,000+ per year in research and legal advisory time |
|
Total annual savings |
NZD ~1.75 million per year (combined appraisal + AskKen AI) |
|
Microsoft contribution |
NZD $20,000 from Microsoft recognising this as an industry-first Azure build |
Benefits to the Client
- Appraisal turnaround time reduced from 30–45 minutes to under 1 minute — freeing agents to focus on client relationships
- Consistent, professional, branded appraisal reports across all regions and agents — no variation in quality
- EMV accuracy of ±3% nationwide — matching or exceeding experienced agent assessments
- AskKen AI gives every property manager instant access to legislation, case law, market data, and maintenance knowledge without leaving the platform
- Agent profiles, contact details, and property images auto-populated via SSO and API integrations — zero manual formatting
- New property data captured for off-plan and new builds feeds back into the Bayleys Data Lake — building proprietary market intelligence ahead of public availability
- Stress and cognitive load reduced for property managers — repetitive tasks automated, accuracy protected
- Platform scales across New Zealand and Australia from a single codebase
- Recognised by Microsoft with a $20,000 contribution as an industry-first innovation on Azure
Support & Next Steps
Peritos Solutions provided post-go-live support covering monitoring of AI output quality, EMV model tuning, and integration stability. The platform is designed for continuous improvement — as new tribunal decisions, legislation updates, and market data arrive, automated pipelines re-index the RAG knowledge base daily or weekly.
Planned next-phase enhancements include:
- Extension to additional Australian markets and McGrath Real Estate agent base
- Expansion of the Bayleys Data Lake with manually entered new-build and off-plan property data
- Additional AskKen AI modules covering insurance policy guidance and financial modelling
- Business intelligence dashboard tracking appraisal volumes, lead conversion, and referral rates from sales to property management
- Further fine-tuning of the EMV model with expanded suburb-level correlation data
Looking for a Similar AI or Property Technology Solution?
Peritos Solutions specialises in AI-powered applications, ERP integrations, and cloud-native platforms across New Zealand, Australia, USA, and India. We are a Microsoft partner with hands-on experience delivering first-of-kind solutions on Azure.
Get in touch: info@peritosolutions.com | +64-212579909 | www.peritossolutions.com
About the Client
Bayleys Real Estate is New Zealand’s largest full-service real estate agency, operating across residential, commercial, rural, and property management services across New Zealand and Australia. With over 150 property management agents generating 1,800 to 2,000 rental appraisals per month, the manual documentation workload was significant, inconsistent across regions, and a major drain on agent productivity.
The leadership team — including the National Director and Financial Director — identified AI-driven automation as the strategic priority, with a clear mandate: cut appraisal time, improve consistency and accuracy, and free agents to focus on client relationships rather than documentation.
Project Background
Bayleys was already running a modern AWS-hosted property search web application built by Peritos Solutions — giving agents a cloud-based way to search and manage property records from any device. The next phase was to add AI intelligence on top of that foundation.
Each rental appraisal required an agent to manually research comparable properties, write a property description, calculate a market rent range, pull together agent branding and contact details, and format everything into a professional PDF. This 30 to 45 minute process, repeated thousands of times per month, was the single biggest time drain in the property management workflow.
Peritos Solutions was engaged to design and build the AI upgrade: automating the appraisal document, training a mathematical valuation model on historical data, deploying an AI copywriting engine for property descriptions, and building the AskKen AI chatbot for on-demand knowledge access.
Requirements
- Generate a complete, professional, branded rental appraisal report in under one minute — from a single property address entry
- AI-generated property description — trained on thousands of historical Bayleys appraisals to match the tone and style of an experienced property manager
- EMV (Estimated Market Rent) calculated by a machine learning model trained on historical sales and rental data — accuracy within ±3% of experienced agent assessment
- Property attributes (bedrooms, bathrooms, floor area, carparks) automatically retrieved via CoreLogic API
- Property listing image automatically pulled via Bayleys API where the property is currently listed for sale
- Agent profile photo, name, contact details, and office auto-populated via Office 365 Single Sign-On
- School zones and local amenities automatically identified from property address
- Support for multiple property types — house, apartment, unit, minor dwelling, home and income
- Manual entry flow for new-build and off-plan properties not yet in CoreLogic or Bayleys systems
- AskKen AI chatbot — zero-training, conversational interface covering legislation, tribunal cases, market data, maintenance costs, yield calculations, and suburb intelligence
- RAG architecture grounding all AI responses in controlled Bayleys proprietary data — not the open internet
Scope & Feature List
|
Module 1 — Automated Rental Appraisal Report |
|
A property manager enters or confirms the property address. The system generates a complete, professionally formatted, Bayleys-branded rental appraisal report automatically:
|

|
Module 2 — EMV (Estimated Market Rent) Valuation Engine |
|
The EMV engine is the mathematical centrepiece of the platform. Peritos evaluated multiple modelling approaches and selected a Random Forest Regression model, trained on data from the Bayleys Data Lake, as the optimal fit for rental valuation. The model was refined through three stages to achieve ±3% accuracy against experienced agent assessments:
Key technical components:
|
|
Module 3 — AI-Generated Property Descriptions |
|
Property descriptions are generated automatically by an AI model trained specifically on Bayleys‘ historical appraisal data. Rather than producing generic text, the model writes in the tone and style of an experienced Bayleys property manager.
Example output: ‘Large 5-bedroom, 3-bathroom home with triple car garaging, heated swimming pool and spa pool… Located close to Kohimarama Beach and top schools — Kohimarama School and Selwyn College. Whole house (5 beds): $1,650–$1,800pw’ |
|
Module 4 — AskKen AI Legal & Market Chatbot |
|
AskKen AI is a purpose-built real estate intelligence assistant, powered by OpenAI GPT-4O with a custom AI engine layered on top to control output quality and data sourcing. It is accessible via mobile and desktop and requires zero training to use. Architecture — Retrieval-Augmented Generation (RAG):
AskKen AI handles queries across:
|

Solution Architecture

Technology & Architecture
The AI platform is built cloud-native on AWS, with OpenAI -GPT-4O powering the language generation layer. All AI responses are grounded in controlled proprietary data — not the open internet.
|
Layer |
Technology / Service |
Role |
|
Cloud |
AWS (primary) |
Serverless infrastructure, Lambda functions, API Gateway, DynamoDB, S3, SNS, CloudWatch |
|
AI / LLM |
OpenAI GPT-4O |
Base generative and reasoning capability for AskKen AI and property description generation |
|
AI Orchestration |
AWS Lambda + Node.js/Python |
Microservice orchestrating: user input → RAG retrieval → LLM call → answer filtering → UI response |
|
EMV Model |
Random Forest Regression |
Trained on Bayleys Data Lake — bootstrap aggregation, geometric mean, Pearson R suburb weighting — ±3% accuracy |
|
RAG Layer |
Vector store + proprietary docs |
54,000 tribunal cases + legislation + market data indexed — retrieved at query time to ground LLM responses |
|
Data Layer |
Bayleys Data Lake |
Historical appraisals, rental data, property records, new-build manual entries — feeds EMV model training |
|
Property Data |
CoreLogic API |
Bedrooms, bathrooms, floor area, carparks — retrieved automatically on address entry |
|
Images |
Bayleys Listings API |
Current listing photos pulled into appraisal report automatically for listed properties |
|
Auth |
Office 365 SSO |
Single sign-on — agent profile, photo, and contact details auto-populated in every report |
|
Security |
AWS WAF + token auth |
Web Application Firewall + token-based API endpoints — all property and AI data secured |
|
Guardrails |
Rules engine |
LLM outputs reviewed against compliance checklists; unsupported assertions stripped before reaching the user |
Application Images
Implementation Approach
The project kicked off in October 2024 and delivered an MVP into UAT for Auckland agents by early March 2025 — on schedule and within budget:
|
Phase 1 — Discovery |
Requirements workshops, CoreLogic and Bayleys API integration scoping, data lake assessment, RAG document inventory, architecture design on AWS |
|
Phase 2 — EMV Model |
Initial Random Forest baseline, geometric mean refinement, Pearson R suburb-level correlation weighting — iterated until ±3% accuracy achieved nationally |
|
Phase 3 — Appraisal Engine |
Automated report generation, CoreLogic integration, Bayleys API image pull, Office 365 SSO, multiple property type handling, 90-day expiry logic |
|
Phase 4 — AI Descriptions |
GPT-4O fine-tuning on historical Bayleys appraisals, sentiment analysis training, school zone and amenity integration, review and editing workflow |
|
Phase 5 — AskKen AI |
RAG pipeline build, document ingestion (legislation + 54,000 tribunal cases), guardrails layer, GPT-4O prompt engineering, chat interface on mobile and desktop |
|
Phase 6 — UAT & Go-Live |
UAT with Auckland property managers, regional disclaimer configuration, performance tuning, cost optimisation on AWS, go-live and hypercare |
Challenges & Solutions
|
EMV accuracy from ±15% to ±3% |
Initial models had very high variance. Three refinement stages — basic features, geometric mean aggregation, then Pearson R local correlation weighting — drove accuracy to ±3% nationwide, matching experienced agent assessments. |
|
AI descriptions that sound human |
Generic AI property descriptions were immediately identifiable and not fit for purpose. Peritos trained the model on thousands of real historical Bayleys appraisals using sentiment analysis — the output now matches Bayleys‘ own writing style. |
|
New-build data gaps |
Off-plan and new-build properties lack CoreLogic data. A manual entry flow was built, with all entered data feeding back into the Bayleys Data Lake to improve future EMV accuracy in newly developed areas. |
|
RAG grounding vs. hallucination |
LLMs are prone to confident but incorrect legal answers. All AskKen AI responses are grounded in indexed proprietary documents with a guardrails layer that strips unsupported assertions before they reach the agent. |
|
54,000 tribunal case ingestion |
Ingesting and indexing this volume of case law required careful document parsing, metadata tagging by jurisdiction and date, and chunking strategy to ensure relevant cases are retrieved at query time. |
|
First AI project — high visibility |
As Bayleys‘ inaugural AI initiative this project set the benchmark for all future AI investment. Peritos delivered on time, within budget, with quantifiable ROI — and secured a $20,000 Microsoft contribution recognising it as an industry first. |
Financial Impact
|
Appraisal time reduction |
From 30–45 minutes per appraisal to under 1 minute — saving approximately 40 minutes per appraisal |
|
Monthly appraisal volume |
1,800–2,000 appraisals per month (60,000–67,000 annually) |
|
Saving per appraisal |
NZD $33.33 per appraisal (at NZD $50/hr agent cost) |
|
Annual appraisal saving |
NZD $720,000–$800,000 per year from appraisal automation alone |
|
AskKen AI saving |
10 hrs manual research saved per agent/month × 150 agents × NZD $50/hr = NZD $75,000/month |
|
Annual AskKen saving |
NZD $900,000+ per year in research, compliance checking, and legal advisory time |
|
Total annual savings |
NZD ~$1.75 million per year — combined appraisal automation + AskKen AI |
Key Benefits
- Appraisal turnaround time reduced from 30–45 minutes to under 1 minute — freeing agents to focus on client relationships
- AI-generated property descriptions match the tone and style of experienced Bayleys property managers — consistent quality across all agents and regions
- EMV accuracy of ±3% nationwide — matching or exceeding the estimates of experienced agents
- AskKen AI gives every property manager instant access to legislation, tribunal cases, market data, and maintenance knowledge — without leaving the platform
- Agent profile, contact details, and property images auto-populated via SSO and API integrations — zero manual formatting
- New-build and off-plan data captured manually feeds back into the Bayleys Data Lake — building proprietary market intelligence ahead of public availability
- Stress and cognitive load reduced for property managers — repetitive tasks automated, accuracy protected
- Platform scales across New Zealand and Australia from a single codebase on AWS
- Recognised by Microsoft with a $20,000 contribution as an industry-first AI innovation
Support & Next Steps
Peritos Solutions provided post-go-live hypercare covering AI output quality monitoring, EMV model tuning, and integration stability. Automated pipelines re-index the RAG knowledge base as new tribunal decisions and legislation changes arrive — the system improves continuously without manual intervention.
Planned next phase:
- Extension to Australian markets — McGrath Real Estate agent base
- Expanded AskKen AI modules covering insurance policy guidance and advanced financial modelling
- Business intelligence dashboard — appraisal volumes, lead conversion rates, and sales-to-property-management referral tracking
- Further EMV model refinement with expanded suburb-level correlation data from new-build entries
- Automated contact creation in the platform when new landlords are onboarded
Looking for a Similar AI Property or Real Estate Technology Solution?
Peritos Solutions specialises in AI-powered applications, machine learning valuation models, RAG chatbots, and cloud-native platforms on AWS — across New Zealand, Australia, USA, and India.
Get in touch: info@peritosolutions.com | +64-212579909 | www.peritossolutions.com
About the Client
Wine-Searcher is the world’s most visited wine marketplace and price comparison platform, connecting consumers, collectors, and trade buyers with wine retailers across more than 180 countries. With over 8 million distinct wine listings and millions of monthly active users, Wine-Searcher depends on accurate, consistent, and richly detailed product data to power search, recommendations, and pricing intelligence.
The editorial and data team had long relied on a combination of contributor-submitted data and manual verification — a process that created bottlenecks as the catalogue scaled and left the majority of listings without historical or regional context. The leadership team identified AI-driven automation as the path to consistent data quality at scale, with a clear brief: recognise the label, extract the facts, and tell the story.
Project Background
Wine-Searcher already operated on AWS — with a modern data pipeline handling listing ingestion, search indexing, and pricing data. The next phase was to add AI intelligence on top of that foundation: automatically reading wine labels, extracting structured metadata, and generating contextualised provenance summaries that elevate the consumer experience.
Each label presents a unique challenge: typography varies wildly across producers and countries, regulatory text overlaps with brand content, multi-language labels require translation before parsing, and the historical context for a given wine may span decades of regional winemaking history. No off-the-shelf model could handle the full pipeline — a purpose-built solution on SageMaker was required.
Peritos Solutions was engaged to architect and build the end-to-end AI pipeline: image ingestion, a custom label recognition model, OCR-based structured extraction, a RAG-grounded Bedrock summarisation layer, and integration back into Wine-Searcher’s live listings platform.
Requirements
- Automatically identify winery, wine name, vintage, appellation, grape variety, alcohol percentage, and certifications from a label image — accuracy target of >92%
- OCR extraction of all label text, structured into a validated JSON schema compatible with Wine-Searcher’s existing listing data model
- AI-generated historical provenance summary — 150 to 250 words, grounded in a curated wine knowledge base covering regions, producers, vintages, and critics’ scores
- Support for labels in French, Italian, German, Spanish, Portuguese, and English — with automated language detection and translation before structured parsing
- Inference latency under two seconds per label for real-time API use; batch enrichment pipeline for retroactive processing of existing catalogue
- Confidence scoring on every extracted field — low-confidence predictions routed to a human review queue rather than published directly
- RAG grounding for Bedrock summaries — no hallucinated facts about producers, vintages, or regions; all claims traceable to indexed knowledge base sources
- Continuous model improvement — validated human corrections feed back into the SageMaker feature store and trigger incremental retraining
- SageMaker Model Monitor integration — automated data drift detection and accuracy degradation alerts with retraining triggers
- AWS-native security — Cognito authentication, WAF rate limiting, end-to-end encryption, no label image data retained beyond processing window
Scope & Feature List
Module 1 — Label Recognition Engine (Amazon Rekognition + SageMaker)
A wine label image is submitted via API or batch upload. A custom Convolutional Neural Network (CNN) model — trained on a corpus of 500,000+ labelled wine label images and hosted on a SageMaker real-time endpoint — identifies the winery, wine name, appellation, grape variety, vintage year, and alcohol content from the visual label. The model handles skewed angles, low-resolution mobile uploads, partial label occlusion, and multi-label bottle formats (front + back). A confidence score is assigned to each detected field. Fields below the confidence threshold are flagged for the human-in-the-loop review queue rather than written directly to the listing. The SageMaker endpoint is versioned — A/B testing allows new model versions to serve a percentage of traffic before full promotion, with automatic rollback if accuracy degrades. Model training used SageMaker Automatic Model Tuning to optimise hyperparameters across CNN architecture variants.
Module 2 — OCR Structured Extraction (Amazon Textract)
Following visual label recognition, Amazon Textract performs OCR on the full label image — extracting all printed text with bounding box coordinates and confidence scores. A post-processing Lambda function, running in Node.js, applies a Wine-Searcher–specific parsing schema to the raw Textract output: regulatory text is separated from brand content; dates are resolved using regional wine labelling conventions; certifications (organic, biodynamic, AOC, DOC, DOCG) are identified by keyword matching against a controlled vocabulary; and alcohol percentages are extracted from the mandatory legal text band. Multi-language labels are detected by AWS Comprehend and routed through a translation Lambda before parsing. The structured output is validated against the Wine-Searcher listing schema before being written to DynamoDB and pushed to the listings enrichment queue.
Module 3 — Historical Provenance Summary (Amazon Bedrock + RAG)
Once structured label data is confirmed, a RAG pipeline generates a 150 to 250 word historical provenance summary for each wine. Proprietary knowledge base documents — covering wine regions, appellations, major châteaux and producers, vintage quality guides, and critical scoring context — are ingested, chunked, and indexed in an Amazon OpenSearch vector store. At query time, the structured label data (winery, appellation, vintage, grape variety) is used to retrieve the most relevant knowledge base passages. These passages, together with the structured label metadata, are passed to Amazon Bedrock (Claude) as context. The model generates a provenance summary grounded entirely in the retrieved documents — hallucination guardrails strip any claim not traceable to an indexed source. Example output: ‘Château Margaux 2015 is a First Growth Bordeaux from the Margaux appellation of the Médoc. The 2015 vintage was widely acclaimed as one of the finest of the decade — warm, dry conditions produced exceptional concentration, with the Wine Advocate awarding 100 points. Produced primarily from Cabernet Sauvignon with Merlot, Petit Verdot, and Cabernet Franc, this wine is expected to peak between 2030 and 2060.’
Module 4 — Human-in-the-Loop Review & Continuous Learning
Low-confidence label predictions and any Bedrock summary flagged by the guardrails layer are routed to a Wine-Searcher editorial review queue — a lightweight web UI where specialists can confirm, correct, or reject AI outputs before publication. All validated corrections are written back to the SageMaker feature store. An automated retraining trigger fires when the volume of corrections for a given producer category exceeds a configurable threshold — a SageMaker Pipeline runs the incremental training job on the updated feature set, evaluates accuracy against a holdout set, and promotes the new model version to the endpoint if performance improves. This closed loop ensures the model improves continuously as Wine-Searcher’s catalogue grows and new producers are encountered.
Solution Architecture
The platform is built cloud-native on AWS. All AI inference runs within the Wine-Searcher AWS account — no label image data leaves the AWS environment. The architecture is fully serverless outside of the SageMaker inference endpoint, with pay-per-request Lambda functions handling orchestration, parsing, validation, and API integration.
AWS architecture — API Gateway → Lambda orchestration → SageMaker endpoint (label recognition) → Textract OCR → Bedrock RAG summarisation → DynamoDB enrichment store → listings API push → CloudWatch + Model Monitor
Technology & Architecture
|
Layer |
Technology / Service |
Role |
|
Cloud |
AWS (primary) |
Serverless infrastructure — Lambda, API Gateway, DynamoDB, S3, SNS, CloudWatch |
|
Label Recognition |
Amazon Rekognition + SageMaker |
Custom CNN model trained on wine label images — winery, vintage, appellation, grape variety detection |
|
OCR Extraction |
Amazon Textract |
Extracts structured text from label scans — wine name, producer, region, alcohol %, certifications |
|
AI Summaries |
Amazon Bedrock (Claude) |
Generates historical provenance summaries from extracted structured data + retrieved knowledge base context |
|
ML Training |
Amazon SageMaker |
Model training, versioning, A/B endpoint testing, feature store, and batch inference pipeline |
|
RAG Layer |
SageMaker + OpenSearch |
Wine knowledge base (regions, châteaux, vintages, critics) indexed and retrieved at query time to ground Bedrock summaries |
|
Data Pipeline |
AWS Glue + S3 Data Lake |
Label image ingestion, transformation, enrichment, and storage — feeds training pipeline and inference cache |
|
Listings API |
Wine-Searcher Internal API |
Pushes enriched label metadata and AI summaries back into live product listings |
|
Auth & Security |
AWS Cognito + WAF |
Secure API access — rate limiting, token auth, IP-based WAF rules protecting the inference endpoint |
|
Monitoring |
CloudWatch + SageMaker Model Monitor |
Data drift detection, prediction quality tracking, automated retraining triggers when accuracy degrades |
Implementation Approach
|
Phase 1 — Discovery |
Requirements workshops, label image corpus assessment, Data Lake scoping, AWS architecture design, SageMaker feasibility study, RAG knowledge base inventory |
|
Phase 2 — Data Pipeline |
Label image ingestion pipeline via AWS Glue, S3 staging and normalisation, Textract OCR extraction, structured JSON output schema definition |
|
Phase 3 — SageMaker Model |
CNN training on labelled wine image dataset, SageMaker hyperparameter tuning, A/B endpoint deployment, accuracy benchmarking against manual expert classification |
|
Phase 4 — RAG & Bedrock |
Wine knowledge base build (regions, châteaux, vintages, critics), OpenSearch indexing, Bedrock (Claude) prompt engineering, hallucination guardrails, summary quality evaluation |
|
Phase 5 — API & Listings Integration |
Wine-Searcher internal API integration, enriched metadata push back to listings, search index update pipeline, caching layer for inference results |
|
Phase 6 — UAT & Go-Live |
Accuracy UAT with Wine-Searcher editorial team, performance and cost tuning on AWS, SageMaker Model Monitor activation, go-live across 8M+ listings, hypercare |
Challenges & Solutions
|
Low label image quality |
Many label images in the marketplace were low-resolution, tilted, or partially obscured. SageMaker training used augmentation pipelines (rotation, blur, contrast variation) to make the model robust across real-world upload quality. |
|
Multi-language label text |
Wine labels appear in French, Italian, German, Spanish, Portuguese, and English. Textract was supplemented with a language-detection Lambda routing non-English extractions through a translation layer before structured parsing. |
|
Vintage ambiguity |
Older bottles often carry multiple dates (bottling, release, vintage). A custom post-processing rule engine was built to resolve date ambiguity using regional norms (e.g. Bordeaux vs. New World labelling conventions). |
|
Hallucination in historical summaries |
Early Bedrock outputs included plausible-sounding but fabricated château histories. A RAG grounding layer with a curated wine knowledge base (regions, producers, vintages, critics’ scores) was introduced — all summaries now cite indexed sources. |
|
Cold-start for rare producers |
Small-production wineries had few training images. A human-in-the-loop review queue was built so that low-confidence predictions are flagged for expert validation and fed back into the SageMaker feature store for incremental retraining. |
|
Scale of batch enrichment |
Retroactively enriching 8M+ existing listings required a SageMaker batch transform job spread across spot instances — completing in 72 hours at a fraction of on-demand cost, with checkpointing to handle interruptions gracefully. |
Financial Impact
|
Time saved per label |
15–20 minutes manual research and transcription reduced to under 2 seconds automated |
|
Monthly new label volume |
60,000+ new SKUs ingested monthly across contributor uploads and editorial additions |
|
Saving per label |
USD $12–$16 per label at USD $50/hr data team cost (conservative estimate) |
|
Annual data team saving |
USD $8.6M–$11.5M per year from automated label enrichment alone |
|
Historical catalogue enrichment |
8M+ existing listings retroactively enriched — equivalent of 1,600+ person-years of manual work completed in 72 hours via batch transform |
|
Consumer engagement uplift |
Listings with provenance summaries show 34% higher click-through and 22% higher add-to-cart rates vs unenriched listings |
|
Total annual value |
USD $10M+ combined — data team savings + engagement-driven revenue uplift |
Key Benefits
- Label recognition and structured data extraction in under 2 seconds — replacing 15 to 20 minutes of manual research per SKU
- Provenance summaries grounded in a curated wine knowledge base — no hallucinated producer histories, no fabricated critical scores
- Multi-language support across French, Italian, German, Spanish, Portuguese, and English — single pipeline, zero separate tooling
- Confidence-scored outputs with a human-in-the-loop queue — accuracy protected, with validated corrections feeding continuous model improvement
- SageMaker Model Monitor detecting data drift and triggering retraining — the model stays accurate as new producers and regions are encountered
- 8M+ legacy listings retroactively enriched via batch transform — years of backlog cleared in 72 hours at spot instance cost
- 34% higher click-through and 22% higher add-to-cart on enriched listings — provenance data demonstrably drives consumer engagement
- Fully AWS-native — no label image data leaves the Wine-Searcher AWS environment; WAF, Cognito, and end-to-end encryption throughout
- Serverless outside of the SageMaker endpoint — scales to any ingestion volume without infrastructure management
Support & Next Steps
Peritos Solutions provided post-go-live hypercare covering model accuracy monitoring, Bedrock summary quality review, and AWS infrastructure optimisation. Automated pipelines re-index the wine knowledge base as new vintage guides, regional legislation, and critic publications are added — the RAG layer stays current without manual intervention.
Planned next phase:
- Sommelier AI — a conversational Bedrock-powered assistant integrated into Wine-Searcher’s consumer app, capable of food pairing, cellar management advice, and vintage comparison
- Fake label detection — a secondary SageMaker model trained to identify counterfeit and mislabelled bottles using visual and metadata anomaly detection
- Auction & secondary market intelligence — provenance summaries extended with auction price history, rarity scoring, and investment potential indexing
- Visual similarity search — a SageMaker embedding model enabling consumers to search by label image rather than text query
- Expansion of the wine knowledge base — additional appellations, small-production natural wine producers, and emerging New World regions
Looking for a Similar AI / ML Platform on AWS?
Peritos Solutions specialises in AI-powered applications, machine learning pipelines, RAG chatbots, and cloud-native platforms on AWS — across New Zealand, Australia, USA, and India.
Get in touch: info@peritosolutions.com | +64-212579909 | www.peritossolutions.com
About HR Mind
HR Mind is a global resourcing company founded in 2010 that offers end-to-end recruitment and HR solutions to organisations in domestic and international markets. With deep expertise across multinational and local businesses, HR Mind provides tailored talent acquisition solutions across eight industry verticals: Infrastructure/EPC, Internet/E-Commerce, Renewable Energy, Automotive, FMCG, Information Technology, Healthcare, and Industrial/Manufacturing.
The company serves four distinct client segments — MNCs, SMEs, Startups, and Joint Ventures — placing candidates at senior and middle management levels as well as running global talent acquisition mandates. Beyond recruitment, HR Mind also provides HR solutions including payroll outsourcing, salary analysis, and candidate assessment services.
With a large and growing pipeline of job openings across multiple industries and client types, HR Mind faced a scalability challenge: the volume of resumes received per job opening was growing faster than their recruiter team could manually process. A technology solution was needed to automate the screening step without sacrificing the quality and accuracy that HR Mind’s clients expected.
The Problem
Recruitment at scale is fundamentally a data matching problem — but one that had been solved manually for decades. HR Mind identified several specific pain points driving the need for an AI solution:
- High volume, low signal — hundreds of resumes received per job opening, with the majority not matching the role requirements. Manually reading each one to determine relevance was the single biggest time drain in the recruitment process
- Inconsistent screening — different recruiters applied different criteria when reviewing the same JD, leading to inconsistent shortlists and missed candidates
- JD complexity — Job Descriptions often contain 20–40 specific skills, qualifications, and experience requirements. Matching these manually against a resume was error-prone and incomplete
- Keyword blindness — resumes use different terminology for the same skills (e.g. ‘ML’, ‘Machine Learning’, ‘Artificial Intelligence’, ‘Deep Learning’) — manual reviewers often missed valid candidates due to vocabulary differences
- No objective scoring — shortlisting was subjective. There was no quantitative score to explain why one candidate ranked above another, making it difficult to justify shortlists to clients
- Slow time-to-shortlist — delivering a qualified candidate shortlist to a client took 2–5 days from job opening. In competitive talent markets, this delay cost placements
- Inability to re-use candidate pool — past resumes in the database were not being systematically re-matched against new job openings — a significant lost opportunity
Scope & Feature List
|
Module 1 — Job Description (JD) Parsing & Keyword Extraction |
|
The platform begins every recruitment workflow by intelligently parsing the Job Description to extract the structured requirements the AI will match resumes against:
|
|
Module 2 — Resume Ingestion & Classification |
|
Resumes are ingested in bulk from multiple sources and automatically classified before matching begins:
|
|
Module 3 — JD-to-Resume Keyword Matching Engine |
|
The core intelligence of the platform — matching each resume against the parsed JD using multi-layer keyword and semantic analysis:
|
|
Module 4 — AI Candidate Ranking & Shortlist Generation |
|
The ranking engine takes match scores and produces a prioritised, explainable shortlist for the recruiter:
|
|
Module 5 — Recruiter Intelligence Dashboard |
|
A centralised interface giving HR Mind recruiters full visibility of the pipeline, AI results, and candidate insights:
|
Solution Architecture
The platform is built entirely on AWS serverless architecture — no servers to manage, automatic scaling with application volume, and pay-per-use pricing that keeps costs proportional to usage:
|
Layer |
AWS Service / Technology |
Role in HR Mind Platform |
|
Ingestion |
AWS S3 |
Secure storage for all uploaded resumes (PDF, Word, text) — triggers Lambda functions on upload for automatic processing |
|
Document Parse |
AWS Textract |
Extracts structured text from PDF resumes including scanned documents — feeds clean text to the NLP pipeline |
|
NLP / AI |
AWS SageMaker + Lambda |
ML models for resume classification, keyword extraction, semantic matching, and candidate scoring — deployed as serverless endpoints |
|
Text Embeddings |
Amazon Bedrock |
NLP entity extraction and semantic understanding — identifies skills, job titles, organisations, and dates from unstructured resume text |
|
Matching Engine |
AWS Lambda |
Serverless function orchestrating JD parsing, keyword extraction, resume-to-JD matching, and score calculation — triggered per job opening |
|
API Layer |
Lambda Direct URl |
RESTful API endpoints for recruiter dashboard, resume upload, JD submission, shortlist retrieval, and candidate search |
|
Data Store |
SQL DB |
NoSQL database storing structured candidate profiles, match scores, JD keyword profiles, shortlists, and recruiter actions |
|
Auth |
Auth0 |
Recruiter and admin authentication — role-based access to platform features and candidate data |
|
Monitoring |
AWS CloudWatch |
Performance monitoring, error alerting, Lambda invocation metrics, and cost tracking dashboards |
|
Security |
AWS WAF + IAM |
Web Application Firewall protecting API endpoints; IAM roles enforcing least-privilege access to all AWS resources |
|
Storage Archive |
S3 Lifecycle Policies |
Automatic archival of old resumes to S3 Glacier — cost management for long-term candidate data retention |
End-to-End Workflow
|
Step 1 — JD Upload |
Recruiter uploads or pastes the Job Description into the platform. The NLP engine parses it and extracts a structured keyword profile with weighted categories. |
|
Step 2 — Keyword Review |
Recruiter reviews the extracted keywords, adjusts weights if needed, adds custom terms, and confirms the JD profile. The AI is now primed for matching. |
|
Step 3 — Resume Upload |
Resumes uploaded in bulk (PDF/Word) via drag-and-drop or sourced from the existing candidate database. AWS S3 stores each file and triggers automatic processing. |
|
Step 4 — Classification |
Each resume is classified into a role category by the ML model. The NLP pipeline extracts structured data: skills, experience, education, job titles, and tenure. |
|
Step 5 — Keyword Matching |
Each parsed resume is matched against the JD keyword profile. Exact and semantic matches are scored. Skills gaps are identified. An overall match score (0–100) is calculated. |
|
Step 6 — Review & Export |
Recruiter reviews the ranked shortlist, filters by threshold if needed, compares top candidates side-by-side, and exports the final shortlist for client presentation. |
|
Step 7 — Database Update |
All candidate profiles and scores are stored in DynamoDB. As new JDs are posted, stored candidates are automatically re-evaluated — making the talent pool smarter over time. |
Challenges & Solutions
|
Resume format diversity |
Resumes arrive in PDF, Word, scanned images, and plain text. AWS Textract handles all formats including scanned PDFs — ensuring no resume is unreadable by the system. |
|
Vocabulary mismatch |
Candidates and JDs use different terms for the same skill. Semantic NLP embeddings via Amazon Comprehend identify conceptually similar terms, preventing valid candidates from being missed. |
|
Explaining AI ranking to clients |
Clients needed to understand why a candidate ranked where they did. The platform generates a transparent score breakdown per candidate — every ranking decision is explainable. |
|
Scaling for peak volume |
Recruitment campaigns can generate hundreds of applications overnight. AWS Lambda’s serverless model scales to process any number of resumes in parallel with no infrastructure provisioning required. |
|
Bias in recruitment |
Automated ranking risks encoding historical bias. The scoring model is built on skills and experience alignment only — personal identifiers are excluded from all scoring calculations. |
|
Stale candidate database |
Stored resumes quickly became outdated if not re-evaluated. The platform automatically re-scores all existing candidates against each new JD — keeping the talent pool continuously active. |
|
Multi-industry keyword sets |
HR Mind operates across 8 industry verticals — each with distinct terminology. The keyword taxonomy is industry-aware, with sector-specific skill libraries built for each vertical. |
Key Benefits
- Resume screening time reduced by up to 90% — what took recruiters days now takes the AI minutes
- Objective, explainable candidate ranking — every shortlist position is backed by a transparent score breakdown, not recruiter intuition
- Semantic keyword matching eliminates vocabulary-based false negatives — valid candidates are no longer missed because they used different terminology
- Bulk processing on AWS Lambda — 100+ resumes processed in parallel with no performance degradation or infrastructure cost
- Continuous talent pool intelligence — stored candidate profiles are automatically re-evaluated against every new JD, turning the database into a living, searchable asset
- Faster time-to-shortlist — from days to minutes — enabling HR Mind to deliver shortlists to clients faster and win more competitive mandates
- Multi-industry ready — keyword taxonomies cover all 8 of HR Mind’s industry verticals, with recruiter-adjustable profiles per role type
- Bias-mitigated ranking — scoring based solely on skills, experience, and JD fit — personal identifiers excluded from all ranking calculations
- Strapi CMS deployed in a VM.
- Client-ready shortlist exports — formatted PDF or CSV shortlists with match scores and summaries, ready for client presentation in one click
Implementation Approach
Peritos Solutions delivered the platform in phases, with HR Mind recruiters involved at every stage to validate AI output quality against their own domain expertise:
|
Phase 1 — Discovery |
Recruitment workflow analysis, JD structure review across 8 industry verticals, resume format audit, keyword taxonomy design, AWS architecture design |
|
Phase 2 — Data Pipeline |
AWS S3 ingestion setup, Textract PDF parsing pipeline, resume text extraction and cleaning, DynamoDB schema design for candidate and JD profiles |
|
Phase 3 — NLP & ML Models |
Resume classification model training, keyword extraction pipeline (Amazon Comprehend + custom), semantic embedding layer for vocabulary mismatch handling |
|
Phase 4 — Matching Engine |
JD keyword extraction, weighted scoring algorithm, semantic matching layer, composite ranking engine, skills gap analysis module |
|
Phase 5 — Dashboard |
Recruiter interface build — React.js frontend, API Gateway integration, bulk upload UI, ranked shortlist view, candidate comparison, export functionality |
|
Phase 6 — Testing & Tuning |
Recruiter validation of AI shortlists vs manual shortlists — model tuning to align AI output with HR Mind domain expertise; bias audit |
|
Phase 7 — Go-Live |
Production deployment on AWS, CloudWatch monitoring setup, recruiter training, hypercare support period, ongoing model improvement pipeline |
Support & Next Steps
Peritos Solutions manages the AWS environment as an ongoing cloud partner — monitoring costs, model performance, and system stability. The AI models improve continuously as more resumes and JDs are processed through the platform.
Planned next phase enhancements:
- Video interview analysis — AI assessment of candidate video interviews, scoring communication skills and cultural fit signals
- Candidate outreach automation — automated, personalised outreach to top-ranked candidates via email and LinkedIn based on match scores
- Salary benchmarking integration — match scores combined with HR Mind’s salary analysis data to provide candidates with market compensation intelligence
- Real-time job board integration — automatic ingestion of applications from job boards (LinkedIn, Indeed, Naukri) directly into the AI pipeline
- Client portal — direct client access to AI-ranked shortlists with the ability to provide feedback that further trains the model to client-specific preferences
- Multi-language resume support — NLP pipeline extended to process resumes in French, Chinese, and other languages for HR Mind’s global operations
Looking for a Similar AI Recruitment or HR Technology Solution?
Peritos Solutions builds AI-powered recruitment platforms, NLP screening engines, and AWS-native HR tech solutions for staffing firms, enterprises, and HR SaaS companies across New Zealand, Australia, India, and USA.
Get in touch: info@peritosolutions.com | +64-212579909 | www.peritossolutions.com
About the Client
Yorker Limited is a New Zealand-based sports-technology company founded to solve one of cricket’s most persistent problems — the inability of grassroots and amateur players to properly track and manage their bowling workloads. Operating from Auckland, Yorker provides digital tools tailored specifically for cricket players, with a focus on reducing overtraining risk and supporting sustainable performance improvement.
Key business drivers included:
- Providing bowlers with accessible, AI-driven training guidance regardless of access to professional coaching
- Enabling coaches and team managers to monitor cumulative bowling loads and prevent overuse injuries
- Delivering personalised speed improvement recommendations based on individual player data
- Building a scalable, cloud-native platform capable of growing with the user base across New Zealand and beyond
Project Background
Cricket bowlers — particularly at grassroots, club, and academy levels — lack access to the sophisticated workload management tools available to professional teams. Without structured tracking, bowlers frequently over-bowl during net sessions, leading to stress fractures, shoulder injuries, and burnout. Coaches rely on manual scorebooks and memory rather than data. Yorker was conceived to democratise performance science for cricket.
Peritos Solutions was engaged to architect and build the full technology stack: a mobile app (Android and iOS), a serverless AWS backend, and an AI layer powered by AWS Bedrock. The goal was to create an intelligent assistant that could answer training questions, suggest improvement pathways, and flag injury risks — all from within the app.
Requirements
- A mobile application for Android and iOS allowing bowlers to log net session bowling loads by delivery type and intensity
- AI-powered training suggestions using AWS Bedrock, providing personalised speed improvement drills based on player history
- Injury prevention intelligence — detecting when cumulative loads approach dangerous thresholds and alerting the player or coach
- Natural language Q&A interface powered by a foundation model, enabling users to ask questions like “How can I bowl faster?” or “Am I at risk of injury?”
- Secure user authentication via Amazon Cognito with individual player profiles and coaching team access
- Serverless, cost-efficient infrastructure using AWS Lambda and API Gateway to scale with demand
- Push notification capability via Amazon SNS for load reminders and AI-generated insights
- Full observability and alerting via Amazon CloudWatch
Solution Overview
The Yorker platform is built on a fully serverless AWS architecture, with AWS Bedrock at the heart of its AI capabilities. The solution consists of four layers: the mobile application, the API and compute layer, the AI intelligence layer, and the data and notification layer.

Technology & Architecture
|
Mobile Platform |
Android (Google Play) · iOS |
|
AI Engine |
AWS Bedrock – Foundation Model (LLM) |
|
Compute |
AWS Lambda (Serverless Functions) |
|
API Layer |
Amazon API Gateway (REST & WebSocket) |
|
Authentication |
Amazon Cognito (User Pools & Identity Pools) |
|
Database |
Amazon DynamoDB (NoSQL – Player & Session Data) |
|
Storage |
Amazon S3 (Training Data, Media Assets) |
|
Notifications |
Amazon SNS (Push Notifications to Mobile) |
|
Observability |
Amazon CloudWatch (Logs, Metrics, Alarms) |
|
AI Prompt Design |
Peritos Solutions Custom Prompt Engineering |
|
Architecture Style |
100% Serverless – No Managed Infrastructure |
|
Region |
AWS ap-southeast-2 (Sydney) |
Scope & Feature List
|
Bowling Load Tracker |
Players log each net session by delivery type (pace, swing, spin), intensity, and volume. The app calculates cumulative weekly and monthly loads, tracking acute-to-chronic workload ratios used in professional sports science. |
|
AI Speed Improvement Suggestions |
AWS Bedrock analyses the player’s logged pace data and bowler profile to generate personalised speed improvement plans — including strength drills, run-up adjustments, and release technique recommendations. |
|
Injury Risk Intelligence |
The AI monitors bowling load trends and compares them against established thresholds. When a risk is detected, Yorker proactively alerts the player and coach via push notification, with a Bedrock-generated explanation and recommended rest plan. |
|
Natural Language Q&A |
Players and coaches can type or speak questions such as ‘How do I improve my pace?’ or ‘Is my workload safe this week?’ AWS Bedrock answers in plain language, citing the player’s own data where relevant. |
|
Coach Dashboard |
Team coaches can view aggregated load data across all squad bowlers, receive AI-generated risk flags, and download session reports — giving coaching staff the oversight previously only available at elite level. |
|
Push Notification Reminders |
Amazon SNS delivers AI-triggered nudges and reminders: log your session, rest day recommended, review your weekly plan — keeping players engaged and safe between sessions. |
AWS Bedrock Integration Detail
AWS Bedrock is the intelligence layer of Yorker. Lambda functions invoke Bedrock’s foundation model API, passing structured player data and a custom-engineered prompt that contextualises the AI response to cricket-specific training science. Peritos Solutions developed a prompt library covering speed improvement, load management, injury prevention, and performance analytics — each prompt template retrieves the relevant player context from DynamoDB before calling Bedrock.

The Bedrock integration handles four primary AI use cases:
- Speed Improvement: Player enters current pace figures; Bedrock returns a structured 4-week training plan with specific drills, strength exercises, and technique cues personalised to the bowler’s style.
- Injury Risk Q&A: Player asks “Am I bowling too much?” and Bedrock analyses their current acute-to-chronic ratio and provides a risk rating (green/amber/red) with an explanation and recommended action.
- Training Load Questions: Open-ended natural language questions about periodisation, recovery, rest days, and session structure are handled by Bedrock with cricket-specific context injected via prompt engineering.
- Performance Insights: At the end of each week, Bedrock generates a narrative performance summary comparing the player to their own historical averages and recommending adjustments for the following week.
Implementation Approach
Peritos Solutions followed an iterative, sprint-based delivery model across 12 weeks:
- Weeks 1–2: Requirements workshops, AWS architecture design, Bedrock model selection and prompt strategy, Cognito user pool setup, DynamoDB schema design
- Weeks 3–4: API Gateway and Lambda scaffolding, Cognito authentication flows, mobile app shell (Android & iOS), core bowling load data model
- Weeks 5–6: Bowling load tracker UI, DynamoDB integration, session logging, acute-to-chronic workload calculation engine
- Weeks 7–8: AWS Bedrock integration — speed improvement prompt, injury risk engine, natural language Q&A endpoint, Lambda prompt orchestration layer
- Weeks 9–10: Coach dashboard, SNS push notification integration, CloudWatch observability setup, performance insights Bedrock module
- Weeks 11–12: End-to-end testing, UAT with Yorker team, Google Play submission, production go-live, hypercare support
Challenges & Solutions
|
Challenge: AI Prompt Accuracy |
Initial Bedrock responses lacked cricket-specific terminology and context. Peritos developed a structured prompt library with domain-specific context injection, significantly improving response relevance for training and injury queries. |
|
Challenge: Load Calculation Complexity |
Calculating acute-to-chronic workload ratios required handling irregular logging patterns and missing data. A robust Lambda function with rolling window calculations and data imputation logic was implemented. |
|
Challenge: Mobile Offline Support |
Players often practice in areas with limited connectivity. Local session caching was implemented in the mobile app, with DynamoDB sync triggered when connectivity is restored. |
|
Challenge: Bedrock Latency |
Initial AI response times were too slow for a smooth user experience. Lambda function optimisation, connection reuse, and streaming response patterns were implemented to reduce perceived latency. |
|
Challenge: Personalisation at Scale |
Each player requires different AI context. A DynamoDB-backed player profile system was built to inject individual history, bowling style, and goals into every Bedrock prompt — personalising responses at scale. |
Benefits to the Client
- AI-powered training suggestions now accessible to grassroots bowlers — democratising elite-level performance science
- Real-time injury risk monitoring reduces the likelihood of overuse injuries through proactive, data-driven alerts
- Coaches gain team-wide visibility of bowling loads without manual tracking, saving time and improving player welfare
- 100% serverless architecture means Yorker scales automatically with the user base at minimal infrastructure cost
- AWS Bedrock eliminates third-party AI subscription costs — all AI compute is metered and cost-effective on AWS
- Secure, privacy-compliant user data management via Amazon Cognito — no player data shared with third parties
- Push notifications via SNS keep players engaged between sessions and reinforce consistent training habits
- Full observability via CloudWatch ensures the team can monitor usage, debug issues, and maintain SLA targets
Support & Next Steps
Peritos Solutions provided two weeks of hypercare post-launch, monitoring Lambda function performance, Bedrock API response quality, and DynamoDB throughput. The Yorker app is now live on the Google Play Store (com.yorker) and is actively being used by cricket players and coaches across New Zealand.
Planned next phases include:
- iOS App Store release (in progress)
- Bedrock fine-tuning with real Yorker user data to further improve suggestion quality
- Video analysis integration — allowing Bedrock to analyse bowling action video clips for technique feedback
- Team/club management features — enabling clubs to manage multiple players and compare squad load data
- Integration with wearable devices for automated session detection and delivery counting
Looking to Build an AI-Powered Mobile App on AWS?
Peritos Solutions specialises in AWS cloud architecture, AI/ML integration with AWS Bedrock,
and mobile application development across New Zealand, Australia, USA, and India.
Get in touch: info@peritosolutions.com | +64-212579909 | www.peritossolutions.com
About Client
Electric Kiwi is an autonomous online New Zealand electricity retailer. Established in 2014, Electric Kiwi uses cloud computing and intelligent meters to service customers nationwide in major urban areas. Its services depend on the presence of the smart meters in the customer’s home. For the client, we did the POC for integrating AWS Support Services with Datadog’s CloudFormation template.
- http://www.electrickiwi.co.nz/
- Location: New Zealand
Project Background
The case study of the project provides a synopsis of how we did the POC for the client for integrating AWS Support Services, an AWS account with Datadog employing Datadog’s CloudFormation template. Creating an IAM role and associated policy enables Datadog’s AWS account to make API calls for collecting or pushing data into your AWS account. Using the CloudFormation template supplies all the tools required to send this data to your Datadog account, and Datadog helps the CloudFormation template to provide the latest functionality. The template even deploys the Datadog Forwarder Lambda operation for sending logs to Datadog.
After setting the initial connection, enable the individual AWS service integrations appropriate to your AWS domain. With a single click, Datadog provisions the required resources in your AWS account and starts analyzing the metrics and events for the services you use. For general AWS services you are using, Datadog needs out-of-the-box dashboards providing prompt and customizable visibility. The project background demonstrates setting up the integration and establishing the Datadog Agent on an Amazon Linux EC2 instance and feeds a broad outline of the integration’s capabilities. Visit the Enable integrations for individual AWS service factions for a list of the general sub-integrations.
This procedure can be repeated for multiple AWS accounts as required, or you can also use the API, AWS CLI, or Terraform to set up various accounts simultaneously. For more details, read the Datadog-Amazon CloudFormation guide.
Scope & Requirement
The scope & requirements involved the following:
- Datadog integration with AWS support services to measure and accomplish observability matrix
- Identified costing
- Updated pricing with partner discount as applicable
- Shortlisted services for which we did POC
- EC2, database Monitor Requirement, Steps, and Dashboard View
- Along with pricing and cost for using Datadog; for monitoring and analytical purpose
Implementation

Technology and Architecture
Technology/Services used
We used Datadog integration with AWS services to masure and do observability matrix and helped them to setup below
- Cloud: AWS
- Shortlisted services for which we did POC
- Organization setup: Control tower
- Policies setup: Created AWS service control policies
- Templates created for using common AWS services
Security & Compliance:
- Tagging Policies
- Azure config for compliance checks
- NIST compliance
- Guardrails
- Security Hub
Backup and Recovery
- AWS Backup provided a simple, secure, cost-effective, and cloud-based backup solution which was already implemented for the client
Network Architecture
- Site to Site VPN Architecture using Transit Gateway
- Distributed Azure Network Firewall
- Monitoring with Cloud Watch and VPC flow logs.
Cost Optimization
- Alerts and notifications are configured in the AWS cost
- Identified Costing
- Updated pricing with partner discount as applicable
Code Management, Deployment
- Cloudformation scripts for creating stacksets and scripts for generating AWS services was handed over to the client
Challenges
- Access was not provided to the actual environment and setting up
- Complex environment setup and monitoring for production cost was only possible to evaluate if we have got the access for the actual environment from the client
Support
- 1 month of extended support
- A template for Cloud formation stack to create more AWS resources using the available stacks
- Screen-sharing sessions with a demo of how the services and new workloads can be deployed.

About Client
The world today is witnessing a growing trend in the use of technology in the health sector. This allowed us to assist our client, a pharmaceutical company in tracking medical devices and the quality of medicines on the go along with the inventory and transit status, and we supported them in AWS to IoT integration.
Project Background
In this case study, we achieved the following:
- How we implemented a small AWS IoT integration application with a toolkit to assure product quality, elevate the efficiency of medical devices, and raise alerts in case manual intervention is required
- Set up AWS for the application to manage the devices seamlessly
- Interaction with the device to fetch vital information
- Finally, creating a mobile application and using AWS IoT to monitor the devices
Scope & Requirement
We used the below solution components to create a responsive web application that gives a holistic view of all the devices connected to the system and information on their vital parameters.
Implementation

Technology and Architecture
Technology/ Services used
We used AWS services and helped them to setup below
- Cloud: AWS
- Organization setup: Control tower
- AWS SSO for authentication using existing AzureAD credentials
- Policies setup: Created AWS service control policies
- Templates created for using common AWS services
Security & Compliance:
- Tagging Policies
- AWS config for compliance checks
- NIST compliance
- Guardrails
- Security Hub
Network Architecture
- Site to Site VPN Architecture using Transit Gateway
- Distributed AWS Network Firewall
- Monitoring with Cloud Watch and VPC flow logs.
Backup and Recovery
Cloud systems and components used followed AWS’s well-Architected framework and the resources were all Multi-zone availability with uptime of 99.99% or more.
Cost Optimization
Alerts and notifications are configured in the AWS cost
Code Management, Deployment
Cloudformation scripts for creating stacksets and scripts for generating AWS services was handed over to the client
Challenges
- We encountered some issues as below:
- AWS setup and pricing were complicated to understand as it is based on usage and consumption, which was a difficult thing to assess at the start of the application
- Ensuring data privacy and security is of utmost importance in this case. Since devices can be hacked without much effort due to poor encryption and that could allow unauthorized access
- Impeccable quality assurance of the whole setup was to be achieved in this case of the pharmaceutical industry, which involves dealing with medicines are surgical instruments, so there was a need for honest sharing of information if anything was not going as expected.
- Understanding the client’s vision of how they needed the UI was challenging.
Support
- 1 month of extended support
- A template for Cloud formation stack to create more AWS resources using the available stacks
- Screen-sharing sessions with a demo of how the services and new workloads can be deployed.










