Independent design & development
EST. IN INTENT / BUILT IN REALITYIntent,
made real.
Digital products, distinctive websites and practical AI automation. From the first question to a working system.
01 /Expertise
Design with purpose.
Built to work.
A product, a website or a connected workflow. The form follows the task, not a template.
Digital products
Web apps, portals and internal tools. Structure, prototypes, interfaces and development.
02Distinctive websites
Clear positioning, considered interfaces and purposeful motion, built for everyday use.
03AI & connected workflows
Automation and integrations for repetitive work, with human review where it matters.
From positioning and interface to implementation — the decisions stay connected.
02 /Working studies
Three studies.
Real interactions.
No more “where are we with this?”
A shared view of the project. Progress, next steps and the decision that needs your attention.
- A single source of project status
- Clear approval states
- An obvious next action
A better client experience.
Interface direction, v.02
The workspace structure is ready to review.
Every request has a place to go.
A small operations queue that makes ownership and priorities visible before anything gets lost.
- Filter the work that needs attention
- Keep responsibility explicit
- Close the loop on completed work
Requests
03From a message to a useful brief.
An example of an AI-assisted intake flow: extract a draft, review it, then decide what happens next.
- A structured first draft
- Human review before action
- A visible confirmation step
Prepared samples. No live AI or external data transfer.
Self-initiated studies. Fictional scenarios and data. Working interactions. Changes stay in this page and reset on reload.
03 /The process
From question
to working release.
A written scope, deliverables and price before production begins. Progress you can inspect along the way.
- 01
Define the task
Clarify the audience, the task and the decisions the product needs to support. Define a useful first release and its boundaries.
Outcome: a defined problem and scope - 02
Give it a form
Structure, key screens and visual direction. Make the essential decisions tangible before implementation.
Outcome: a reviewable product direction - 03
Make it work
Implement the agreed release with AI-assisted development. Check the real user journeys, edge cases and handling of data.
Outcome: a tested working release - 04
Hand over with clarity
Deliver the agreed source, setup instructions and operating notes. Define maintenance needs and the next practical step.
Outcome: a product you can keep operating
04 /Independent by design
One conversation.
Connected
decisions.
VOLIFACT brings product thinking, distinctive visual design and AI-assisted implementation into one independent practice.
You work directly with the person shaping the product. The visual choices, system logic and implementation stay part of the same conversation.
A good fit
A clear business task, a decision-maker and a first release small enough to get right.
Clear boundaries
Payment infrastructure, regulated decisions and security-critical systems need specialist expertise and are outside this offer.
05 /Before we start
Before we begin.
What if I don’t have a technical brief?
Start with what happens today, where it breaks down and what a better outcome would look like. Defining the product is part of the work. You do not need to arrive with a technology choice or a specification.
Can this work with the tools I already use?
That is assessed during scoping. Existing APIs, access rights, service limits and recurring costs are checked before an integration is promised. Sometimes a smaller change to your current setup is the better answer.
How is AI used in the work?
AI supports research, design and implementation; the output still needs review and testing. AI inside your product is optional. Sensitive data, external services and approval boundaries are agreed before use.
What will it cost, and how long will it take?
The quote follows the scope. You receive the proposed deliverables, price, dependencies and milestones before committing to production. A focused first release is preferred to an open-ended rebuild.
What happens after handover?
The agreement defines source delivery, documentation, third-party licences and any support period. Ongoing maintenance is scoped separately, so responsibilities and costs stay clear.
06 /Start a conversation
What would you
like to
make?
A new product, a more expressive website or a process worth automating. Tell me what you have in mind and what needs to change.
Your inquiry is reviewed for fit. Then we clarify the problem, the scope and the practical next step.