Our approach
Fewer meetings, more working software
You see something running in a browser in the first two weeks. Everything after that is a conversation about a real thing, not a slide.
Our story
Cignova started in 2014 with two people who were tired of shipping sites they were not proud of. We are eleven now and the rule has not changed: we would rather turn work down than hand over something we would not use ourselves.
Our vision
A web that is fast on a cheap phone, usable with a keyboard, and readable without an account. Most of what we build is an argument that this is also the commercially better option.
Our values
Say the inconvenient thing early. Quote what it will cost, not what wins the pitch. Leave the project in a state where someone else could take it over — and be glad if they never have to.
How it works
Four steps, start to launch
Understand
One week on content, journeys and constraints — what exists, what is missing, what someone came here to do.
Design
The two most important journeys become something clickable in a real browser, at real widths, in week two.
Build
Weekly releases to a staging URL you can open any time. No month-long silences, no big reveal.
Launch & stay
We handle the migration, watch the first weeks closely, and stay on for maintenance if you want us to.
Why us
What you get that you will not get elsewhere
Direct access to the people building it, code you own outright, and a studio that answers the phone a year later.
- You talk to the people writing the code, not to an account manager
- Maintenance that keeps the site fast and safe long after launch
12+ years building for the web
Questions
The things everyone asks first
A brochure site is typically six to eight weeks; a store or an application, three to five months. The variable is almost never our speed — it is how long content and approvals take on your side, which is why we agree those dates up front too.
Yes, entirely, from the first day. The repository is yours, the design files are yours, and there is no licence to renew. If you decide to work with someone else later, nothing has to be bought back.
That is the point of the CMS we build for you. Fields are named for what they are, previews match what publishes, and there is no way to break the layout by editing text. We train your team and leave written notes.
A maintenance plan if you want one: updates, monitoring, offsite backups, small changes included, and a short monthly note about what changed. If you would rather handle it in-house, we hand over documentation and answer questions for free for the first three months.
Often. Plenty of sites need their performance, accessibility or checkout fixed rather than a rebuild. We audit first and tell you honestly which of the two you are looking at, even when the answer is the cheaper one.