From idea to live product
A model on its own is not a product. The work is in the interface, the data, the edge cases, and everything people touch every day.
That is the part I build.
01 — What I Do
AI consulting, from the first question to a working system
You might know exactly what you want to build, or just have a task that takes too much time. I help you decide where to start, build the software, and get it working with the systems you already use.
-
S/01
Web & Mobile Product Development
Take an idea through design, development, and launch. I build the application, connect payments and accounts where needed, and include AI where it helps the experience.
A working product, with the code and documentation to maintain it.
-
S/02
Voice & Live AI Applications
Applications that respond to speech and react to what is happening on screen. That could be a voice assistant, a guided training session, or a companion that talks a user through a task.
A voice experience built around the people who will use it.
-
S/03
AI Features Inside Your Product
Add AI to software you already run: search across your own content, assistants your customers talk to, generated drafts your team reviews. Built with testing, approvals, and cost controls.
A feature your users notice, not a demo in a side tab.
-
S/04
Advisory & Opportunity Review
A focused review of what you are building and where AI genuinely helps. I look at your product, your data, and your roadmap, then estimate the effort involved.
A prioritized plan, a proposed scope, and a clear next step.
02 — Experience
Ten years of shipped products
I’m Norris Chebl, an AI consultant and software engineer based in San Diego. I’ve worked as a founding engineer across three ventures, building voice applications, commerce tools, and software that brings live data together. When we work together, you work directly with me.
- 10+ years writing software professionally, at startups and as a consultant
- 100+ projects built for clients, startups, and products of my own
- Founding engineer first engineer hired at three companies, twice building the product from nothing
03 — Working Together
Start with one useful thing
-
01
Agree on the scope
We talk through the problem, look at your current process, and choose a first project. You get a written scope, a price, and a timeline before development starts.
-
02
Build and test with your team
I share a working version early so the people using it can give feedback. We test it against real tasks, check the outputs, and review running costs as we go.
-
03
Launch and hand it over
I help put the system into use, document how it works, and walk your team through it. If you need ongoing support or want to build on it, we agree on that separately.
Built for your team
You own the custom code and control the accounts. I build in your infrastructure and document the setup, so your team can maintain the system after handoff.
04 — Common Projects
What that can look like
A few examples of the problems I can help with. The right approach depends on your process, your data, and who will use the result.
- Internal document search
- Customer request triage
- Document processing
- Report preparation
- Customer record updates
- Voice assistants
- Interactive training
- Live data dashboards
- Payment workflows
- Web & mobile applications
05 — Questions
Before we get started
I’m not sure where AI would help. Can we start there?
Yes. Tell me which tasks take too much time or cause the most frustration. We can start with an audit to work out what is worth building. Sometimes a simpler automation is the better answer.
How long does a project take?
An audit usually takes about a week. A focused first build can take two to six weeks; a larger product takes longer. I’ll confirm a timeline after reviewing the scope, your data, and any integrations.
Who owns the code and the accounts?
You own the custom code and control the accounts used to run it. I document the setup and any third-party dependencies so your team can take over after handoff.
How will you handle our data?
Before development, we agree on what data the system needs, where it is stored, and which providers may process it. Access, retention, and logging are part of that discussion. We can also cover any confidentiality requirements.
Can we work together without an engineering team?
Yes. I can handle the build and help you plan for ongoing operation. If you already have engineers, I work with them and provide the documentation and tests they need to maintain it.
How is pricing handled?
Audits have a flat fee. Development is priced by phase, with a scope agreed before work starts. If the scope changes, we agree on the cost before I do the extra work. Send me a short description of your project and I can help define the first phase.
Where are you based, and do you work remotely?
I’m based in San Diego, California, and work remotely with teams across the US and internationally. We agree on meeting times and how we’ll share progress at the start.