AI Opportunity & Product Direction
Find the valuable problem before choosing the technology. Define what the product must change, who it serves and how success will be proved.
DISCOVERY · PRODUCT LOGIC · COMMERCIAL FITFounder-led AI product architecture
Polar Systems designs connected AI products around real commercial problems—combining product thinking, workflow intelligence and rapid development to move from idea to working system.
What I actually do
My role is not traditional software engineering and I do not pretend it is. I define the product, map the decisions and workflows, shape the user experience and use AI-assisted development to turn that architecture into working systems.
My main focus is building Polar: a connected family of intelligent products. I also take on a small number of outside projects where AI can remove genuine friction, improve a decision or unlock an entirely new service.
Where Polar Systems adds value
Find the valuable problem before choosing the technology. Define what the product must change, who it serves and how success will be proved.
DISCOVERY · PRODUCT LOGIC · COMMERCIAL FITMap the signals, rules, human judgement and operational steps so AI becomes part of a coherent system—not another disconnected tool.
SIGNALS · DECISIONS · ACTIONS · SAFEGUARDSMove quickly from a difficult idea to something people can see, use and challenge. Learn from the working product instead of debating slides.
PROTOTYPE · TEST · LEARN · REFINEConnect intelligence to the platform, data and people already doing the work, with explicit human control and a practical route to adoption.
INTEGRATION · AUTOMATION · GOVERNANCETurn the working system into a focused mobile experience for the people doing the job—connected to the same intelligence, data and decisions rather than becoming another isolated app.
IOS · ANDROID · CONNECTED WORKFLOWSThe Polar laboratory
An intelligent operating platform for HVAC businesses—designed to help teams find work, win work, save time, run better and grow.
Explore Polar One SAAS + MOBILE / SMALL BUSINESS02A SaaS platform with a connected mobile application, designed to guide an owner from idea and launch through everyday control, first invoice and sustainable growth.
Explore the platform BUSINESS INTELLIGENCE03A focused Polar product for turning business signals into clearer priorities, better decisions and practical next actions.
Explore Polar Optimiser LOCAL INTELLIGENCE04A developing local intelligence concept exploring how businesses can find and act on opportunities in the communities around them.
Explore Polar LocalPolar live intelligence
Describe one recurring frustration. The AI Project Builder will give you one clear product idea, show how it would work in everyday life and explain exactly what we would build first.
How the work moves
Understand the real work, friction and desired outcome.
Map the system, intelligence, actions and human control.
View a sample architecture ↓Create a focused working product quickly enough to learn.
Test it against real use, evidence and commercial value.
Connect what works and expand without losing simplicity.
Illustrative project architecture / version 01
A sample technical plan showing how Polar Systems turns a commercial problem into a controlled, testable product—not simply a collection of AI features.
Success is defined before technology is selected: quicker first response, clearer ownership and fewer opportunities disappearing without a recorded outcome.
Email, web forms and agreed enquiry sources
Extract need, urgency, value indicators and history
Apply business rules and explain the recommendation
A person reviews messages and important actions
Prepare reply, assign owner and schedule follow-up
Record outcome and improve the agreed rules
Bring approved enquiry channels into one controlled intake.
Create one reliable enquiry record with customer and history context.
Classify the request and recommend priority with a visible reason.
Give the owner a clear review, approval and follow-up screen.
Keep the decision, action, outcome and rule version together.
"Why does this enquiry need attention now?"
Idempotent event intake, schema validation and a queue for background processing, retry and dead-letter handling.
POST /v1/enquiries/eventsTenant-scoped enquiry, customer, action and outcome records. Object storage only where documents are genuinely required.
PostgreSQL · encrypted backupsDeterministic gates handle known policy. The model returns validated structured output with confidence and supporting signals.
{ priority, reason, action, confidence }Classification, enrichment and follow-up tasks run independently with timeouts, retry limits and visible failure states.
queue · retry · dead-letterRole-based access, tenant isolation, secret management, encryption in transit and at rest, and explicit retention controls.
RBAC · TLS · tenant_id boundaryStore model, prompt and rule versions alongside latency, cost, errors, approval and outcome for measurable review.
trace_id · model_version · audit_eventAgree the sources, fields, retention period and access before the pilot begins.
Customer messages and commercial decisions remain visible and reversible.
Record the reason, rule version, approval and eventual outcome.
Map the real enquiry journey, failure points, owners and trusted data.
OUTPUT / VERIFIED WORKFLOWDefine information boundaries, decision rules, controls and measures.
OUTPUT / AGREED SYSTEM PLANConnect one source and build the smallest useful review experience.
OUTPUT / WORKING PILOTRun alongside the current process, compare outcomes and refine safely.
OUTPUT / 30-DAY EVIDENCEIs a valuable enquiry noticed sooner?
Are agreed next steps actually completed?
How many enquiries still disappear without an outcome?
Do people agree with the priority and reason?
Architecture principle: prove one valuable decision before expanding the system. Technology choices follow the workflow, data and control requirements—not the other way round.
Discuss an architectureStart with the problem
You do not need a specification, a technology choice or the perfect terminology. Describe the recurring problem and what a better outcome would change. That gives us something useful to think about together.
What is repeatedly going wrong or taking too much effort?
Who feels the problem and what does it cost in practice?
What would become possible if it worked differently?
Selective project availability