Problem
We start where it hurts, not with a technology shortlist. The brief is whatever is genuinely in the way.
Everyone wants new technology automation AI software Almost nobody starts with the problem
Don't get lost in the noise. Tools are meant to empower, not burden you. We're here to help you stay focused.
Most businesses do not have a technology problem, They have a system problem.
New tools get bought to paper over processes that were never designed. The tool gets blamed. Another tool gets bought.
We work the other way around. Understand the commercial problem, agree what a good outcome is worth, redesign the system that produces it — and only then decide what technology belongs there. Sometimes that is an application. Sometimes it is a workflow. Sometimes it is deleting a step nobody questioned.
How we think about this
01
The problem
What is actually costing you time, margin or momentum.
02
The outcome
What good looks like, stated in commercial terms.
03
The system
The process and the data that have to change first.
04
The technology
Only then, and only as much as the system needs.
01 Proof
Outcomes, stated in the language the business already uses.
0%
-
Operational time recovered across an automated workflow.
0x
-
Throughput on the same headcount after the system changed.
0 days
-
From first conversation to a working system in production.
02 Method
Six steps, and the first three happen before anyone writes code.
The same structure runs through every case study, so you can see exactly where a project turned.
Constraint
Budget, team, data, timeline, appetite for change. Constraints decide what a good answer even looks like.
Thinking
We work out the shape of the system before anyone opens an editor. This is the part most projects skip.
System
Process, data and decisions designed as one thing, so the software has something coherent to stand on.
Implementation
Built and shipped — application, automation, integration or all three, using whatever the system actually needs.
Outcome
Measured against the commercial result we agreed at the start, not against the size of the deliverable.
03 Capabilities
Four capabilities. One decision about which of them the problem needs.
You should not have to pick a service before you have spoken to anyone. Bring the problem; we will tell you which of these it touches.
Growth
Positioning, offer and funnel work grounded in how the business actually earns.
- Positioning & offer
- Funnel architecture
- Lifecycle & retention
- Measurement
Growth
Growth
AI
Applied where it changes the economics of a task — and honestly ruled out where it does not.
- Applied LLM workflows
- Retrieval & knowledge
- Decision support
- Evaluation
AI
AI
Automation
Repetitive operational work removed from people and put into systems that can be trusted.
- Workflow design
- Integrations
- Data plumbing
- Monitoring & alerting
Automation
Automation
Tools
Custom applications when the off-the-shelf answer stops fitting the way the business runs.
- Web applications
- Internal tools
- APIs & services
- Dashboards & reporting
Tools
Tools
04 Work
What happens when that thinking gets applied.
Case studies are written as arguments, not galleries: problem, constraint, thinking, system, implementation, outcome.
05 Thinking
How Ryan thinks, published in the open.
An editorial publication inside Funnel135 rather than a company blog. Often the first thing anyone reads.
Do you need Hermes if you already use ChatGPT or Claude?
Hermes is not a better chat window. It is useful when a good answer has to become a durable operation.
Do you need Hermes if you already use ChatGPT or Claude?AI Search Is Still SEO, Until It Isn’t
AI search has not made SEO obsolete. But ChatGPT Ads in Malaysia mean organic visibility and paid discovery are beginning to occupy the same …
AI Search Is Still SEO, Until It Isn’tChatGPT Use Is Not Business Capability
More people using AI does not automatically mean a business has built a capability. The difference is whether a recurring piece of work now …
ChatGPT Use Is Not Business Capability
06About
One person accountable for the thinking, with the technical ability to make it real.
Funnel135 exists because the gap between business advice and working software is where most projects die. Strategy decks that nobody can build. Builds that nobody questioned. The point of this practice is to hold both ends at once.
Complexity belongs behind the interface.
Ryan — Founder, Funnel135