C-01
Quoting and pricing engines
Spec sheets, RFQs and email threads in. Priced, formatted quotes out. Days compress to minutes without losing your pricing logic.
The problem
You can see it everywhere except inside your own company.
Every week there is another story about AI transforming an industry. Then you walk into your own building, where the quoting still runs on a spreadsheet somebody built in 2006 and nobody has fully understood since.
You are not short of ambition. You are short of anyone in the building who can tell you which of it is real, what it would cost, and whether it would survive contact with the way your business actually works. So the decision keeps getting deferred — and every quarter it's deferred, a competitor with better internal machinery quotes faster, ships faster and takes a little more of your market.
That distance has a name. When what a company can see is possible stops matching what it can actually execute on a Tuesday morning, the business has gone dissonant — the market playing in one key, your operations in another. We took the name from the problem, because closing that interval is the only thing we do.
Symptom
Software you bought two decades ago that everyone complains about and nobody can replace.
Symptom
No internal expertise, so every vendor sounds equally credible and equally expensive.
Symptom
The nagging sense that you should have started eighteen months ago.
Target profile
Two kinds of CEO call us.
Both run real companies with real revenue and internal systems that stopped keeping up somewhere around 2014. The only difference is whether the pain is visible yet.
Profile 01 — measurable loss
You already feel it.
A competitor turns quotes around in an hour. You take three days, and you know exactly why: four people re-keying the same order into three systems that were never meant to talk. The loss is already on your P&L. You just don't have anyone in the building who can fix it.
- Deals lost on response time, not price
- Headcount growing faster than revenue
- One retiring employee understands the database
- Six SaaS subscriptions, none integrated
You already know what's broken. Tell us in a few lines and we'll scope it — fixed price, fixed timeline, in writing.
Scope my project
Profile 02 — invisible ceiling
You can't see it yet.
You read about AI constantly and none of it maps to your business. Nobody on your team has built with it, so nobody can tell you what's actually on the table versus what's noise. The gap isn't costing you visibly — which is precisely the problem. We put a number on it in week one.
- No internal benchmark for what's possible
- Vendors selling seats, not outcomes
- Core processes unchanged in a decade
- Institutional knowledge trapped in people
You don't know what's possible yet. We ask the questions, map your workflows and come back with what's worth building.
Run the analysisApproach
We are not here to sell you AI.
We are here to make your operations faster. Most of the time in companies like yours that means AI, because the bottleneck is reading, sorting, matching and re-typing — exactly the work that has become cheap in the last three years. Sometimes it just means a properly built piece of software. We'll tell you which one you're looking at, build it, hand it over, and stay reachable long after the invoice is closed.
01 — We've built the products
Twenty years combined across SaaS, growth and AI/ML. We founded and shipped our own venture-funded product, so we know what it costs to build something that has to keep running.
02 — And built them for others
Internal AI systems delivered inside large corporates, through their security reviews and against their legacy databases. Not a lab, not a proof of concept.
03 — We stay current, deliberately
This field moves monthly. Knowing what became possible last quarter is most of the job, and it is the part your team cannot do while also running the company.
Industrial distribution · 240 staff
Quoting engine over a 1990s parts catalogue
Inbound RFQs arrive as PDFs, faxes and email threads. The system reads them, matches parts against their legacy catalogue, applies their pricing rules and returns a formatted quote for a human to approve.
Three days → nineteen minutes
Read the case study
Logistics · 90 staff
Document intake into a legacy TMS
Bills of lading and customs paperwork read, validated and posted automatically.
Four FTE of re-keying removed
Read the case study
Precision manufacturing
Forty years of drawings, searchable
Every job file, tolerance sheet and revision queryable in plain language before the last engineer retired.
Knowledge retained
Read the case study
Valve manufacturing · 4 sites
Scheduling off the spreadsheet nobody understood
The planning sheet that ran four sites was rebuilt as a real system with the original logic intact, then extended to forecast load across all of them. No rip-and-replace, no retraining the floor.
On-time delivery 71% → 94%
Read the case study
Two operators, and a network behind them.
We work with a standing network of vetted engineers, designers and specialists we have shipped with before. When a project needs more scale, or you need it faster than two people can move, we bring them in — vetted already, no search, no ramp-up. They are managed by us and carried by us, and the cost sits inside the fixed price we quoted before the work started. You never receive a second invoice and you never manage a contractor you didn't choose.
Capability
What we actually build.
Not strategy decks. Working internal systems, deployed on your infrastructure, running your business.
C-02
Document and order intake
Purchase orders, invoices and supplier PDFs read, validated and pushed into your ERP. No re-keying, no swivel-chair integration.
C-03
Institutional memory
Forty years of drawings, contracts and job files made searchable in plain language, so knowledge stops walking out at retirement.
C-04
Legacy system bridges
The AS/400, the Access database, the spreadsheet that quietly runs scheduling. We build around them rather than forcing a rip-and-replace.
C-05
Internal agents and copilots
Tools your staff actually open: support triage, sales research, ops reporting. Built to your process, not a generic template.
C-06
Go-to-market systems
Pipeline, outbound and reporting rebuilt with the same discipline. Optional, and only once the operational side is solid.
Deployment
Prove it in four weeks. Scale it once you believe it.
You should not have to bet a six-figure budget on people you met last month. So the engagement is staged: a small, fixed-price pilot that puts one working system into your business, and a full build you only commission after you've watched the first one run.
Stage 00
Diagnostic
Week 1–2
We talk. If you already know what's broken, we scope it directly. If you don't, we run the analysis ourselves — we ask your team the questions that surface where the time and money are going, and map the workflows behind it.
You get a written gap analysis: what's costing you, roughly what it's worth to fix, and what we'd build first. It's yours whether or not you continue.
No chargeNo commitment either
Stage 01
Pilot build
Four weeks
We build the single highest-value system from the diagnostic and put it into production with the people who'll use it. Not a demo, not a slide — a working tool your team opens on a Monday morning.
Fixed price, agreed before we start. If it doesn't do what we said it would, you don't proceed to stage two.
From $15KFixed · scoped in week two
Stage 02
Full build
Scoped after the pilot
Once the pilot is running and you've seen what it changed, we scope the rest: the connected systems, the harder integrations, the parts that needed the first win to justify.
If scale or speed demands more hands, we pull from our vetted network — managed by us, inside the quoted price. Ends the same way every project ends — source code, documentation, training, and we step out. Reachable afterwards, on your side of the phone.
CustomQuoted to scope · always fixed
Why we can move this fast
Two owners, no account layer and no discovery theatre. The person scoping your project is the person building it, which removes the translation step that makes agency timelines what they are. Where a project needs more hands we bring in our network — but we never bring in a layer between you and the build.
We leave. We don't disappear.
Handover means you stop paying us, not that you stop hearing from us. If something breaks in month four, if a supplier changes their file format, if a new person needs walking through it — you email or call the two people who built it and you get an answer. There is no ticket queue, no support tier and no invoice for a question. The point of this model is that you own a system that works, and a system nobody can ask about isn't one.
Terms of engagement
You own it. Completely.
The software industry sells you a tenancy. We build you an asset. Pilots start at $15K, and full builds are quoted to scope — always as one fixed number agreed before any work begins, network resources included.
| Dimension | Software vendor | Dissonant |
|---|---|---|
| Cost structure | Per seat, per month, forever | One fixed project fee |
| Data residency | Their cloud, their terms | Your infrastructure, your terms |
| Source code | Licensed to you | Transferred to you |
| Roadmap | Their priorities, their timeline | Built to your requirements |
| Renewal leverage | Reset every twelve months | Nothing to renew |
| If we disappear | Your system stops | Your system keeps running |
| After handover | Support tier, ticket queue | Our direct numbers, no meter running |
| Cost in year three | Compounding | Zero |
Operators
Two operators. No junior bench.
Twenty years of combined experience across SaaS, growth and AI/ML. The two people who scope your project are the two people who build it, and we are both owners — so neither of us can hand you off to an account manager.
Ten years in go-to-market, first as head of growth inside martech companies, then co-founding Genpage with Ceyhun and taking it through venture funding. Samy runs the first conversation, then runs the project. Scope discipline, UI and UX, weekly communication, and everything else that isn't code — so there is one person accountable for delivery rather than a shared inbox.
- Before
- Head of growth, martech
- Founded together
- Genpage — venture-funded martech SaaS
- Owns
- Diagnostic, scope, delivery, UI/UX, comms
Ten years in AI and ML engineering, most of it delivering internal systems inside large corporates, before co-founding Genpage with Samy as its technical lead. He has already met your security review, your undocumented database and your one skeptical engineer. Ceyhun writes the code himself, and pulls in and directs our vetted network when a build needs more hands.
- Before
- AI/ML engineering, large corporates
- Founded together
- Genpage — venture-funded martech SaaS
- Owns
- Architecture, build, handover
Common questions
Before you ask.
What does this actually cost?+
The diagnostic is free. Pilots start at $15K for four weeks and a working system in production. Full builds are quoted to scope — the number comes out of what the pilot proved, not a rate card. Every figure is fixed and agreed in writing before work starts, including anyone we bring in from our network, who never appears as a separate invoice.
What if the pilot doesn't work?+
Then you stop, and you've spent the price of a pilot rather than the price of a transformation program. That's the entire reason the engagement is staged. The scope document says exactly what the pilot must do, so there is no argument at the end about whether it did it — and if we miss what we committed to, we fix it before we invoice the balance.
How do we know AI is even the right answer for us?+
Sometimes it isn't, and we'll say so. We're not AI evangelists — we're here to make your operations faster, and occasionally that means a well-built piece of ordinary software. In practice, most companies like yours are bottlenecked on reading, matching, sorting and re-typing, and that is precisely the work that became cheap in the last three years. The diagnostic tells you which situation you're in before you spend anything.
Who maintains the system after you leave — and can we still reach you?+
Yes, always. Handover ends the invoice, not the relationship: if something breaks, if a format changes, or if a new hire needs walking through it, you call or email us directly and you get an answer. No ticket queue, no support tier, no meter running. Day to day the system is maintained by your own team, because we deliberately build with standard, boring technology that any competent developer can pick up — and if you'd rather we handle ongoing work formally, a retainer is available. But that's a choice you make later, not a dependency we design in.
Does our data leave our environment or train someone's model?+
No. Systems are deployed inside your infrastructure or a cloud tenancy you control, with model providers configured for zero data retention. We'll walk your IT or security team through the architecture during scoping.
You're two people. What if our project is bigger than that?+
We keep a standing network of vetted engineers, designers and specialists we've shipped with before, and we scale the team up whenever the work demands it — whether that's because the scope is large or because you need it delivered faster. They're pre-vetted, so there's no search and no ramp-up, and they're managed and paid by us inside the fixed price you already agreed. What never changes is that the two of us stay on the project from the first conversation through to handover.
We hired a consultancy before and got a slide deck. Why is this different?+
A consultancy sells you analysis and staffs delivery with juniors. We sell you a working system in four weeks, and the two people you meet are the two people who build it. If nothing ships, we've failed — there is no deliverable here that isn't running software.
Our systems are genuinely old. Is that a problem?+
It's the entire practice. Most of what we build sits alongside an AS/400, an Access database or a spreadsheet that quietly runs scheduling. We bridge to what exists rather than demanding a replacement your business can't afford to survive.
How much of my team's time does this take?+
A few hours across the diagnostic, from the two or three people who know the process best, then a weekly check-in during the build. Far less than any software implementation you've done, because we adapt to your workflow instead of making you adapt to a product.
Intake
Tell us what's broken.
A few lines is enough. We take on a small number of engagements per quarter, and we'll come back within two business days with an honest read on whether it's worth scoping — or a straight no.
Rather just talk+33 0 00 00 00 00
Rather book a slotTwenty minutes with Samy
Rather emailhello@dissonant.co