Explore what we build.
Web platforms, mobile applications, connected systems and internal tools. Bring your requirements to a technical scoping call.
This guide sets out what each capability is for, who it fits and who it does not, what you receive, and the terms that apply to every build. It is written for enterprise and government leaders, growing businesses and funded founders alike. Read and compare it without giving an email address.
- Engagement
- A fixed price for a defined scope, or a time-based rate for open-ended work, agreed after discovery
- Acceptance
- Written criteria agreed before work begins, reviewed at milestones, used for sign-off at handoff
- After launch
- Reproducible defects in the agreed scope corrected when reported within 90 days
- Led by
- Aladdin Hamed, founder, leads every build hands-on
Start from the problem
- Staff lose hours to a workflow no product fits, or clients need a secure place to see their own records.Start withWeb platforms
- The product depends on the phone itself: offline use in the field, the camera, or push notifications.Start withMobile applications
- Work varies from case to case, and software should plan and act inside your systems with a person approving anything irreversible.Start withAgentic systems
- Systems must exchange data reliably, releases cannot be rolled back, or nobody has restored a backup.Start withAPIs and infrastructure
- The team runs the business from spreadsheets and back-office screens that were never designed for the work.Start withInternal tools
- A brochure site, or one integration between two tools.Start withSaffron Designs or Saffron Automations
The five capabilities
Web platforms
A workflow that costs staff hours every week or produces errors, and no off-the-shelf product fits it without contortion.
- A good fit
Several subscriptions held together by copying and pasting between them.
Clients or partners who need a secure place to see their own records, documents or status.
An existing application that works but that nobody can safely change any more.
- Not the right fit
A brochure site or landing page. Start with Saffron Designs.
A commodity function that a mature product already does well, such as accounting or payroll. Buy it.
- What you receive
Scoped in the blueprint for your project. As the work requires: identity and roles, the data model, typed interfaces, the console, integrations, background work and an audit trail.
Decision records and a runbook. Delivery acceptance requirements: Lighthouse 95 or higher and WCAG 2.2 level AA, verified before handoff.
Mobile applications
The product depends on the phone itself: offline use in the field, the camera, or push notifications.
- A good fit
Customers or staff who do the work away from a desk and need what the device can do.
- Not the right fit
Most use happens at a desk. A web platform is usually faster to build and easier to change.
- What you receive
An app for iOS, Android or both, as the agreed scope sets out, prepared for release through the app stores.
Offline use, sync and push notifications where the product needs them.
Agentic systems
Work that varies from case to case, where software should plan, call tools and act inside your systems, with a person approving anything that cannot be undone.
- A good fit
The agent has to live inside your own product or infrastructure, integrate with systems no standard tool reaches, or meet requirements a managed service cannot, such as your own hosting, audit or data residency.
- Not the right fit
The steps never change. A deterministic program is cheaper, faster and easier to test.
Nobody can say what a correct outcome looks like, so there is nothing to evaluate against.
An outcome in your operations, delivered as a service. Start with Saffron Automations.
- What you receive
Narrow typed tools, scoped permissions, approval gates, an action log, limits on cost, time and steps, and an evaluation suite of real tasks.
The source, prompts, tool definitions, evaluation suite and runbook at handoff.
APIs and infrastructure
The parts that never make the demo and decide everything: how systems exchange data, whether a release can be rolled back, whether a backup restores.
- A good fit
A product or platform whose interfaces, deployments or recovery cannot be trusted today.
- Not the right fit
One integration between two tools. Start with Saffron Automations.
- What you receive
Scoped in the blueprint for your project. As the work requires: typed interface contracts, observability, release pipelines with checks and rollback, and backups restored in a test before launch.
Internal tools
The console your team lives in: the dashboards and back-office screens that decide how quickly work gets done.
- A good fit
A team running the business from spreadsheets, or from screens that were never designed for the work it repeats every day.
- Not the right fit
A commodity function that a mature product already does well, such as accounting or payroll. Buy it.
A tool with a short life. A low-code platform can be the right answer there.
- What you receive
Scoped in the blueprint for your project. As the work requires: dashboards, back-office consoles and automation platforms designed around the tasks your team repeats most, built to be operated for years.
Terms that apply to every build
The signed engagement agreement for each project sets out the binding terms. These are the commitments it is built on.
Acceptance is agreed before the build.
We agree written acceptance criteria before work begins, review them at milestones and use them for sign-off at handoff.
Choose an engagement that fits the work.
A fixed price for a defined scope, or a time-based rate for open-ended work, agreed after discovery.
What you own.
You own the code written for you and the infrastructure it runs on; reusable Saffron components come with a permanent licence to use them. Open-source libraries and third-party services stay under their own licences, with paid accounts in your name.
After launch.
Every build includes correction of reproducible defects in the agreed scope, reported within 90 days after launch. New features, ongoing maintenance and changes made by other parties are agreed separately.
Who does the work.
Aladdin Hamed, founder of Saffron, leads every build hands-on, with specialists brought in when a project needs them.
Bring your requirements to a technical scoping call
A short brief, then a 30-minute call. You will hear plainly whether Saffron Systems is the right fit for the work, and what it would take.