ESEN
Tell us what you need

FROM NEED TO PROPOSAL

Know what you are commissioning.

Scope, budget, delivery and ongoing costs. These are the decisions we clarify before starting development.

A FIRST PROJECT

Choose where to start.

Start with a defined need. We agree on scope, deliverables and budget before development.

01

Automate one process

Your team repeats the same steps across email, documents and applications.

We start with one defined workflow, its rules and its exceptions.

What we can deliver

  • Process map and agreed scope
  • Integration with validation and alerts
  • Testing, user guide and handover

We need process examples and authorised access to the tools involved.

Automate my process
02

An assistant with your knowledge

Finding information or answering recurring questions takes too much time.

We define one task, approved sources and when a person takes over.

What we can deliver

  • Defined sources and permissions
  • Prototype with reviewable answers
  • Testing and oversight criteria

We need authorised documentation and examples of real questions.

Define my assistant
03

The first version of your product

You need a tool, platform or app that fits the way your business works.

We prioritise essential users and workflows for a useful first release.

What we can deliver

  • Prioritised workflows and features
  • Software and agreed integrations
  • Technical handover and evolution plan

We need the goal, users and systems the product should connect to.

Define my product
Each proposal confirms the final deliverables and acceptance criteria.Scope, budget and maintenance

What your proposal should make clear

A scope you can review

We define users, one priority workflow, integrations and acceptance criteria. You can see what the first delivery includes and what is reserved for later.

A budget with its assumptions

Complexity, existing systems, data quality and publishing requirements affect the estimate. Development, third-party services and maintenance are itemised in the proposal.

A plan based on dependencies

We plan stages after reviewing the work, access and content required. Missing API permissions, decisions or store approvals can affect the schedule.

A technical handover

We agree on documentation, access and how the delivered solution will be operated. Ownership, licences and responsibilities are stated in the proposal.

What happens after delivery?

Hosting and infrastructure

Where the solution runs, who manages it and how backups and monitoring are handled.

External services and AI usage

Model usage, messaging, storage and third-party licences can have their own fees. We identify these dependencies and agree spending controls.

Support and improvements

We agree on incident handling, updates and future work. Response times and any ongoing service are specified in the proposal.

Tell us about one process or product.

Share the task, the tools you use and what you want to improve. We will review the context and define the next step with you.

Discuss my project Explore an example first