Big ideas deserve clear answers. Explore how we design, what shapes a project and what happens next—so you can move forward with confidence.
20 answers to explore. Search to narrow them down.
Good questions make better starting points. Here are three conversations that help turn an exciting idea into a project with a clear direction.
Start with the audience, the essential outcome and the pages or features needed to support it. A clearer scope gives the design a better foundation.
Your services or product idea, who it is for, the main action a visitor should take, any must-have content and existing systems that need to connect. We can discuss what is still unknown.
The number of page types, content readiness, functional requirements, integrations and review process all influence the project plan.
We clarify the requirements before agreeing scope, deliverables, timing and cost. If you have a deadline or a budget range, include it in your enquiry so the conversation can start in the right place.
Editing access, hosting, domain arrangements, third-party services and ongoing support need to be clear before the project is complete.
Who will update the content, where the website or application will run, which services it depends on, and whether maintenance or support is included. These arrangements are defined for your project.
Business websites, focused landing pages and website refreshes. The page structure and visual approach depend on your audience, offer and the action you want visitors to take.
Yes. We discuss custom SaaS MVPs, customer portals and internal tools. The first step is defining the user, the core workflow and the useful outcome, then agreeing the functionality and dependencies.
No. Start with your business or idea, the people it is for and what you want to improve. The project brief tool helps turn those essentials into a useful outline.
Share your main objective, audience, service or product, key requirements, preferred timing and budget range if known. Existing brand assets, content and references can help us understand the direction.
Content responsibilities are agreed for the individual project. Bring the copy and assets you have. If you need help shaping content or sourcing imagery, raise it during scoping so the work and any costs can be considered.
Yes. Share your logo, colours, fonts and any guidelines. We can discuss how the identity translates into the website or application, and whether any additional design work is needed.
Responsive design is part of the approach. Content flow, navigation and controls are considered for desktop, tablet and mobile. The specific devices and browser checks are agreed within the project.
Yes. Transitions, reveals and interactive feedback can be included in the agreed scope. Motion should support the experience and respect reduced-motion preferences; the level of animation depends on the design and technical requirements.
Potentially. We need to check the service being connected, account access, subscription costs, API availability and the intended journey before confirming what can be included.
These can be discussed during planning. Authentication, role permissions, payment providers, data handling, hosting and maintenance responsibilities need a clear technical scope.
Pricing depends on the scope, complexity, content and features. We discuss the requirements before providing a project-specific proposal. Hosting, domains, third-party tools and optional services should be clarified separately.
A schedule is agreed after the requirements and dependencies are understood. The size of the project, availability of content and review stages all affect the timeline.
The review stages and included feedback process are agreed before work begins. New pages, additional features or a major change of direction may require an updated scope and estimate.
We discuss what you need to edit and who will maintain the site. The editing route depends on the platform and implementation selected for the project. Access and handover expectations should be clear before launch.
Account ownership and hosting responsibilities are agreed during scoping. We clarify which accounts are needed, who controls them and which recurring costs apply.
Maintenance, ongoing changes and support arrangements are discussed for the project. The proposal should make clear what is included at handover and what would be separate ongoing work.
Yes. When you select Send my enquiry, your details are submitted through CORE’s form service and an email notification is requested for the studio. We use the email address you provide to respond. Sending an enquiry does not book work or commit you to payment.
No. Form & field, Orbit and Flow are fictional interface studies used to explain design decisions. They are not live products or completed client engagements, and their sample content is illustrative.
No. Those outcomes depend on your offer, traffic, content, market and other factors. We focus on delivering the agreed design and development work and avoid promising results outside our control.
We discuss the requirements and clarify any open questions. If the project is a fit, the next step is agreeing the work, responsibilities, pricing, timing and review stages before a commitment.
No matching answers. Try another word or select All questions.
Ask about the service, share a challenge or tell us what you want to make. We’ll begin with the details that matter to you.
Your next step starts with understanding.
Pixel