CRM that fits your sales process
Keep opportunities, conversations and next actions together, with the fields and stages your team actually uses.
Custom applications & software
Custom web application development.
Business applications, with AI where it helps.
Your team should not need five spreadsheets to finish one job. We build browser-based business applications that bring your records, decisions and daily work together, with AI where it earns its place.
One workspace for your team and customers, connected to ERP records. AI features are optional.
Illustrative application architectureHow we deliver this service
From your working process to a usable application.
We walk through a real task with its users, model the records and roles, then review a prototype together. We build the first complete journey in increments, connecting the systems and testing the rules behind each screen.
Why work with us
Our founder’s operations and business applications background helps us connect screens with the rules and handoffs behind them. We review working versions with your users, with senior technical oversight before delivery.
The experience behind our approachA good starting point if…
- Your process has rules or exceptions that standard software does not handle well.
- A spreadsheet has become a critical operational application.
- Your staff, customers or suppliers need one application with clear roles, shared records and connected workflows.
See the work
Inside a supplier quote application.
Illustrative example · sample data, not client results.
01 / The problem
Two offers, one incomplete picture
A buyer receives two offers for 200 brackets. One is €12.40 per unit with a delivery date; the other is €12.10 with no date. Email and a comparison sheet leave the follow-up and decision in different places.
RFQ 204 · Quote inbox
2 offers received- Request
- 200 mounting brackets · BRK-20
- Offer A
- €12.40 / unit · delivery 12 November
- Offer B
- €12.10 / unit · delivery not stated
- Sources
- offer-a.pdf · offer-b.pdf
Fictional offers, both in EUR for the same quantity. Freight has not been confirmed.
Sample workspace · read-only
02 / What we do
Compare the terms in one workspace
In the app, the buyer opens the RFQ, compares the same fields and checks the source files. AI can prepare the extracted fields; the buyer checks them and sees which terms still need an answer.
RFQ 204 · Compare offers
Buyer workspace| Check | Offer A | Offer B |
|---|---|---|
| Unit price | €12.40 | €12.10 |
| Goods total | €2,480 | €2,420 |
| Delivery | 12 November | Not stated |
Read the sample source excerpts
Offer A: 200 mounting brackets, BRK-20. EUR 12.40 per unit. Delivery: 12 November. Freight: to confirm.
Offer B: 200 mounting brackets, BRK-20. EUR 12.10 per unit. Delivery and freight: not stated.
Goods totals exclude freight. The missing terms still need checking before a supplier decision.
Sample workspace · read-only
03 / What you get
Know what still needs a decision
The RFQ has one visible status, a task to request missing terms and a decision record. Once the terms are complete, the buyer can choose a supplier and submit the decision for approval.
RFQ 204 · Decision record
Buyer action needed- Current status
- Waiting for delivery and freight terms
- Next task
- Buyer to request missing terms
- Supplier selected
- None — decision pending
- Approval
- Not submitted
Offers, follow-up and the eventual approval stay with the same RFQ.
Sample workspace · read-only
Step 1 of 3
AI can prepare the comparison. The buyer checks the terms, chooses the supplier and submits the decision for approval.
Where it helps
What could your application do?
RFQ and supplier review
Collect offers, compare terms and record approvals in one workspace, with the original documents close at hand.
Operations and customer portals
Manage orders or service requests internally, then give customers a useful view of progress without exposing the whole system.
What’s included
From the user’s first click to a completed task.
A working business application with custom screens, shared records, user roles and integrations, with AI features selected for useful tasks.
Screens for the actual job
Design the records, views and next actions around the people doing the work. Review a prototype before building the first complete journey.
Shared records and clear roles
Build sign-in, permissions, status and business rules so staff, customers or suppliers see the part of the application they need.
Connections and useful AI
Connect existing systems. Add document reading, search or drafting when it helps the task; conventional application logic handles the rest.
A release your team can run
Build in reviewable increments with senior technical review. Test user journeys and access, then prepare deployment, documentation and ownership.
What you receive
The delivery
and the checks.
What needs to work
Users can complete the agreed journey from input to outcome, with working roles, integrations, review states and understandable failure handling.
- Workflow and interface design
- Application with agreed roles and business rules
- Agreed system connections, with AI features where useful
- Acceptance testing and release plan
- Documentation and agreed handover materials
The first conversation
Show us the job your app needs to do.
Walk us through one journey, from the first request to the final decision. We’ll discuss whether an existing product fits, what a first version needs and which dependencies need investigation.
Useful things to share
- Who uses it, and what each person needs to do
- The spreadsheet, screen or sample record used today
- Systems it must connect to and any data to migrate
The next decision: configure an existing tool, explore a prototype or scope a first release. A budget and schedule follow the work needed to define that scope.
Useful answers
Before you
commit.
Should we build or buy?
We check existing products first. A custom build is worth considering when important rules, screens or connections keep forcing workarounds. The comparison includes ownership and maintenance, not only the initial build.
Can we start with a small first version?
Yes. Start with one complete journey, such as submitting a request and getting it approved. A prototype helps check the experience; a first release also needs working data, roles and business rules.
Does the application have to use AI?
No. Our custom AI development services add reading, search or drafting where useful. A conventional business application can be the right answer.
Can you extend our existing application?
Yes, subject to its code, architecture and access. We review those before proposing changes or a rebuild.
What affects cost and timing?
User journeys, roles, migration, integrations and release requirements. We investigate those dependencies before proposing a phased budget and schedule.
What about security, code and maintenance?
We define sign-in, record access and data handling, then test access as well as normal journeys. Hosting, backups, code and account handover, and support responsibilities form part of the project scope. Specific compliance needs must be identified early.
How does this differ from automation?
An application is where people manage work. Automation moves work between steps and tools. A project can combine both, such as automated intake feeding a review application.
Let’s talk about your work
Build a workspace around your team.
Discuss your application buildStart with the process that has outgrown its spreadsheet.
What we’ll discuss ↑← All services