Small on purpose
You work directly with Nigel and the AI team he directs. No account layers, no hand-offs. The work stays close to the person responsible for it.
The studio
Design it well.
Make it work.
Petit Solutions brings design and development to the same table. The job is to make something people want to use, then make sure it does what they need.
Who you work with
A direct
working relationship.
Petit Solutions is Nigel Laguda, working with an AI team he directs. You deal with him directly. No account layers, no hand-offs.
The approach
Start with
the real thing.
A sales conversation. An order moving through the business. A document someone checks every morning. We start with the people, information and decisions behind a project.
That gives the design a purpose and the build a boundary. We agree what a first version should achieve, then make it reviewable in stages.
What the approach means in practice
Engineered properly
Tested code, sensible architecture, real backups, monitoring from day one and documentation a future developer can actually read. Substantial systems, not prototypes dressed up as products.
Yours outright
You own the code, the data, the infrastructure accounts and the intellectual property. If we ever part ways, your system keeps running and someone else can pick it up.
Five stages, typically eight to sixteen weeks for a first working release. You see working software early and often, and you always know what happens next.
01 / Understand
We sit with the work
Find the useful question. Who is it for? What happens today? What needs to work differently? Use real examples to define the problem and the first outcome.
Before a line of code, we spend time with the people doing the job — on the floor, in the office, on the calls. We map the real process, including the parts nobody wrote down.
Discovery Process mapping Stakeholder interviews
02 / Shape
We draw the system
Make the direction tangible. Explore the experience, information and visual language. Agree the scope, price and responsibilities before moving into the build.
Data model, integrations, permissions, failure modes, hosting. Decisions get made on paper where they are cheap to change, and written down so they are never a mystery later.
Architecture Technical spec Fixed scope & price
03 / Build
We build in thin slices
Review something working. Build in useful slices. Test the important journeys with the people who will use them and adjust the details while the work is in view.
Working software every week or two, tested against real scenarios and shown to the people who will use it. Feedback shapes the next slice.
Weekly releases Automated testing User review
04 / Handover
We hand over properly
Know how to run it. Receive the code, accounts and documentation. Agree what maintenance or support is needed and how changes will be handled afterwards.
Source code, infrastructure accounts, documentation, runbooks and training are transferred to you. Your name is on the accounts from day one.
Documentation Team training IP transfer
05 / Support
We stay close, on your terms
You can keep us on for improvements and support as a straightforward monthly arrangement, cancellable with 30 days' notice. Continuing support is your choice, and the handover is designed so the system does not depend on us being in the room.
Support Iteration Roadmap
Built for your business
Yours to
take forward.
A useful tool should remain useful after handover. We make the source, data and account ownership part of the conversation from the start.
- Source code. The materials needed to maintain and develop the build.
- Your accounts and data. Clear access and ownership, with any third-party services identified.
- Documentation. The practical detail needed to run the work and understand its limits.
Hosting, external services and any continuing support are agreed as part of the project.
Off-the-shelf tools can be a useful starting point. When your process no longer fits the product, owning the system changes what you can do next.
Typical SaaS
Rented software
Fast to start. Your choices remain tied to the product.
- Your process bends to fit the product's roadmap.
- Per-seat pricing grows with the number of users.
- Data exports can be technically possible but practically painful.
- Support queues and release notes you did not ask for.
- Tools that do not quite talk to each other.
Petit Solutions
Built and owned
More considered up front. Yours to run and develop.
- The system matches how your team already works.
- No per-seat pricing as your team grows.
- Your data, in your accounts, exportable any time.
- A direct line to the person responsible for the build.
- One coherent system instead of a stack of patches.
Clarity comes first.
A visitor should understand what to do next. A colleague should understand what the system is telling them.
AI needs a defined job.
Choose where it helps, identify what it can get wrong and give a person a clear route to review or correct the result.
Details earn their place.
Motion, imagery and interaction should make the experience more understandable or memorable.
Build for the next person.
Readable code, practical documentation and an explicit handover make a system easier to keep using.
Discovery first
Every engagement opens with a paid discovery. We learn how the work is actually done before we agree scope. If the answer is that you do not need us, we say so.
Fixed scope, fixed price, plain reporting
Builds are quoted on scope, not billed on hours. Ongoing improvement and support comes with a one-page monthly report: what the system did, what was tuned and what is coming next.
Owned, never locked
You own the code, the accounts and the IP. Source code, infrastructure accounts, data and documentation are yours, not held in a proprietary platform. If we part ways, your system keeps running and another developer can pick it up.
Working principle
"If it can't be explained on a whiteboard in ten minutes, it probably isn't the right system yet."
The details behind the experienceIdentity / Type / Material
A system.
Not a collection
of effects.
The identity
Petit SolutionsThe original mark and wordmark stay intact. Their proportions, type and colours hold the identity while the surrounding experience changes.
The type
Aa / 01
Mona Sans gives headlines their width and weight. A steady reading scale and generous spacing keep the practical detail easy to use.
Try the type specimen ↗The material
Ink anchors the interface. Terracotta marks an action or signal. Silver adds depth to the exhibit.
Tap a colour to copy its value.
Start a conversation