What Kalax can help with.
Arrive with a business problem or a known requirement. Technology isn't presumed — but when it's warranted, Kalax designs and builds it.
Problem unclear?
Describe what isn't working. Sam reviews it and recommends a next step — which may not be software at all.
Start with DiagnoseAutomate operations & customer workflows
Workflow automation, WhatsApp and messaging flows, and integrations between the tools you already use.
When this is useful
- The same admin work is repeated by hand every day or week
- Work stalls at handoffs between people or tools
- Enquiries wait too long for a reply or follow-up
- Bookings and customer messages are coordinated manually
What Kalax may do
- Map the current workflow and decide which steps are worth automating
- Build workflow automation with n8n or custom Node.js services
- Set up WhatsApp booking, reminder and follow-up flows
- Connect CRM, calendar and other systems through their APIs
- Keep a human handoff wherever a person should step in
Typical outputs
- Workflow map and automation design
- Deployed automation or messaging flow
- Integrations with your CRM, calendar or other tools
- Error handling and runbook documentation
Technology often involved
- n8n
- WhatsApp Cloud API
- Node.js
- Google Calendar API
- Supabase
Build software & internal systems
Web applications, SaaS products, internal tools and APIs — with AI features only where they are warranted.
When this is useful
- Spreadsheets or off-the-shelf tools no longer fit how the business runs
- Your team needs an internal tool, portal or dashboard
- You are building a SaaS product or MVP
- Existing systems need an API or integration layer
What Kalax may do
- Design the architecture and data model
- Build full-stack web applications
- Implement authentication, databases, APIs and integrations
- Add AI functionality where it serves a real need, not by default
- Set up deployment and hand over documentation
Typical outputs
- Technical architecture document
- Working web application or internal tool
- Database schema and migrations
- Deployment setup and handoff documentation
Relevant proof
Technology often involved
- React
- Next.js
- TypeScript
- Node.js
- Supabase
- PostgreSQL
Make information usable
Private AI search, RAG and internal knowledge systems — or simpler structure and search when that is enough.
When this is useful
- Knowledge is spread across documents, drives and systems
- People spend time finding answers that already exist somewhere
- Sensitive documents rule out public cloud AI tools
What Kalax may do
- Assess whether the problem needs AI at all, or better structure and search
- Build retrieval-augmented generation (RAG) over your documents
- Run local models on your own infrastructure where privacy requires it
- Set up document processing, vector storage and access control
Typical outputs
- Architecture and infrastructure design
- Document ingestion and retrieval pipeline
- Query interface for your team
- Access control and operating documentation
Relevant proof
Technology often involved
- RAG
- Ollama
- LangChain
- PostgreSQL + pgvector
- Docker
Marketing & search intelligence
Technical SEO, measurement and cross-channel analysis — to understand what is and isn't working.
When this is useful
- Channels are reported separately and there is no joined-up view
- It is unclear whether analytics and conversion tracking can be trusted
- Technical issues may be limiting how the site is discovered in search
- You want an evidence-based audit before deciding where to invest next
What Kalax may do
- Technical SEO and discoverability audits
- Review analytics and measurement setup
- Implement structured data and on-page fixes
- Analyse search, ads and analytics data together
- Prioritise recommendations by the evidence behind them
Typical outputs
- Technical SEO audit with a prioritised roadmap
- Measurement and tracking review
- Structured data and on-page changes, where agreed
- Marketing audit findings and recommendations
This is analysis and technical implementation, not a full-service marketing agency — and it comes with no promise of rankings, traffic or leads.
Relevant proof
Technology often involved
- Technical SEO
- Structured data
- GA4
- Google Search Console
- Google Ads
Define before you build
Requirements, PRDs and BRDs, architecture and implementation plans — for when the right next step is clarity, not code.
When this is useful
- The idea is clear to you but not yet written down precisely
- Stakeholders disagree on what should be built
- You need a specification or architecture before choosing who builds it
- A build has stalled and its scope needs to be redefined
What Kalax may do
- Clarify requirements through stakeholder conversations
- Write PRDs and BRDs with user journeys and acceptance criteria
- Design the system architecture and technical specification
- Plan a phased roadmap for implementation
Typical outputs
- PRD or BRD
- User journeys and acceptance criteria
- Architecture or technical specification
- Roadmap and implementation plan
The document or plan is the deliverable. Whether to build next, and who builds it, remains your decision.
Ways to work with Kalax.
Each engagement is scoped to the problem. Not every one leads to a build.
Advisory
From $500/ session
Deeper, deliberate consulting on a specific decision — strategy, architecture or a roadmap — with written recommendations.
- Focused consulting session
- Written recommendations
- Architecture, roadmap or requirements review
- Async follow-up questions
Build
Depends on scope
Delivery of a defined system, from architecture to handover. Scope and cost are agreed before work starts.
- Discovery and architecture
- Build with regular progress updates
- Testing before release
- Deployment and handoff documentation, where applicable
Ongoing
Depends on scope
Continued maintenance, iteration and expansion of systems already in use, scoped around what the system needs.
- Maintenance and fixes
- Planned improvements
- Monitoring, where relevant
Diagnose is different. It's free for now: describe one business problem, Sam reviews it, and you receive a recommended next direction. It isn't Advisory, and any implementation is scoped separately. Start with Diagnose
Have a requirement — or just a problem?
Know what you need? Email the requirement and discuss scope with Kalax. Not sure yet? Start with Diagnose — technology isn't presumed.