Frame
We agree the goal of the product, the main user journeys and the screens that earn their place.
Development
User flows, wireframes and full visual screens, decided and approved before a line of code is written. Design that is tied to a build outcome, not a folder of concepts.
First consultation is free, and every enquiry is answered within 12 hours.
UI/UX design is the work of planning and drawing an interface before it is built: user flows, wireframes and full visual screens you approve. MarkLogix delivers it in Figma, tied to a real website or app build, so the path from landing page to enquiry is decided on paper first rather than discovered in code.
What you get
Every engagement ends with a file a developer can build from without guessing.
We agree the one action each screen should drive and who is taking it, so every later decision has something to answer to.
The routes people take through the product mapped end to end, including the paths that go wrong, before any screen is drawn.
Low-detail layouts that settle structure and hierarchy, reviewed with you so nothing expensive is decided in colour.
Full screens with real type, colour, spacing and imagery, built as reusable components rather than one-off artboards.
Mobile, tablet and desktop layouts for every key screen, because most traffic arrives on a phone.
How elements behave on hover, tap, focus and error, so the build matches the intent.
Contrast, focus order, target sizes and labelling checked against WCAG while it is still cheap to fix.
A tidy Figma file with named components, a type and colour system, and a walkthrough so the build starts without a translation step.
Technology
We are AI first and platform agnostic. The right tool depends on your budget, who maintains it after launch and how far it needs to scale, so we recommend one in the meeting and explain the trade offs before you commit. If your project uses something not on this list, we can still take it on.
Platform licence and subscription fees are paid directly by you, in your own accounts, so nothing is ever locked behind ours.
How it works
We agree the goal of the product, the main user journeys and the screens that earn their place.
Structure and hierarchy in low detail, reviewed and signed off before any visual work.
Full visual screens and components, with revisions built into the stage rather than billed after it.
A developer-ready Figma file, a documented type and colour system and a walkthrough for whoever builds it.
Fit
Investment
Pricing depends on scope, so instead of a fixed number here is what each level of engagement usually covers. The exact figure is confirmed in writing after a free first meeting.
These are estimated starting ranges to help you size a budget. Exact pricing depends on your scope and is confirmed in writing after the first meeting, which is free and carries no obligation.
Questions
A Figma file a developer can build from: user flows, wireframes, full visual screens with real content, responsive layouts, interaction notes and a documented type and colour system. The point is that structural decisions are made and approved before they become expensive to change in code.
It depends on the number of screens, how many user roles and states each has, and whether you need a full component system. A focused set of screens is a small engagement; a full product with a design system is a larger one. We confirm the figure in writing after a free first meeting.
Usually, yes. Most clients have us design and build together, which removes the handover gap entirely. If you have your own developers we deliver a clean, named Figma file and a walkthrough so their build starts without a translation step.
UX is the structure: what screens exist, how people move between them and whether the main action is easy to reach. UI is the surface: type, colour, spacing and imagery. We do both in one engagement because splitting them tends to produce screens that look right but do not work.
Yes. We start by reviewing the current product and, where possible, any analytics, to see where people drop off. You get a written view of what is worth keeping and what should change before design work begins.
Yes. Contrast, focus order, target sizes and labelling are checked against WCAG during design, while fixes are cheap. Every build MarkLogix ships targets a 95 or higher accessibility score, and that is far easier to hit when the design already accounts for it.
Yes. The Figma project is created in your account or transferred to it on completion, with full edit access. Any other designer or developer can pick it up.
Yes. We sign a non-disclosure agreement before you share anything confidential, and we are happy to use your own NDA template rather than ours. We never publish a project as a case study without written permission.
Related
Build the site the design is made for, on the right platform.
Learn moreTurn the approved screens into a working application.
Learn moreSet the logo, colour and type the interface then uses.
Learn moreGet started
Send a few lines about the product. You will get a written recommendation and an indicative price, not a sales call.
Tell us what you need. We reply within 12 hours.
It is on its way to info@marklogix.com and we reply within 12 hours. For a faster answer, send the same details straight to our WhatsApp using the button below.