Skip to content

Find your next step.

Explore the studio

Digital services, delivered remotely

Explain the need clearly. Build the right experience.

Softglimmer helps Bristol businesses turn a broad digital requirement into a practical design and development commission. The work can bring together identity, useful website content, ecommerce, software, mobile applications and connected workflows. We deliver remotely from Ranchi, with the people supplying information and making decisions included in the plan. You can bring an existing site, an early idea or a specific task that needs improvement; discovery helps establish the suitable scope.

View our website work
A complete creative and development brief that makes the intended audience, commissioning contacts and business decisions understandable before implementation.
  1. 01

    Understand the audience

    Explain who will use the result and what they need to accomplish.

  2. 02

    Identify the decision owners

    Separate the person making the enquiry from the people approving the offer and operation.

  3. 03

    Hand over useful work

    Connect the agreed creative files, working functions and everyday responsibilities.

An example journey, shaped around your requirements.

Commission a complete experience with an understandable brief.

A request for a better website may involve unclear service information, a difficult editing process or a customer task that currently happens outside the site. A request for an app may first need clearer rules about users and records. We examine the purpose behind the request, then compare which combination of creative work, content, development and operating preparation fits it.

The engagement can include discovery, information architecture, visual and interface design, implementation, content preparation, migration and selected connections. The brief identifies what you supply and what Softglimmer produces. It also names the person who can confirm a business fact or settle an operating rule. Those decisions prevent a well-presented draft from being mistaken for approved content or a complete implementation.

A focused website and an extensive application deserve the same clarity about their finished outcomes. We describe relevant pages, functions, formats and review tasks rather than using one broad label for different deliverables. The written proposal then gives you a useful basis for choosing the scope, arranging reviews and planning what the receiving team will do after launch.

Give the brief a clear route to an answer.

Useful decisions can come from different people, but they should refer to the same reviewed scope.

01

Who is the result for?

Describe the intended customer, reader, editor or operating colleague. The person arranging the project may be helping another team and may not use the result themselves. Bring that user perspective into discovery before selecting features or judging whether a page has enough information.

02

Who can approve the facts?

Name the people responsible for the public offer, supplied assets and operating rules. A project coordinator can gather comments without automatically becoming the authority for every subject. Record unresolved decisions and their owners instead of making the implementation team guess.

03

What makes the work complete?

Write down the outputs and relevant tasks used to review them. For a design commission, include formats and guidance. For a build, include working journeys, content, editing and agreed connections. Decide how feedback is consolidated and how a later request changes the scope.

Ask for tangible outputs and a working handover.

These six groups provide a useful structure for a tailored proposal, with the exact contents agreed for your project.

01

A shared project brief

An account of the users, desired outcome, supplied information and decision owners. List the current arrangement, constraints and questions still requiring discovery. The brief becomes the reference for reviewing scope and making a reasoned estimate.

02

Information and journey structure

A page plan or task flow showing how people find the right context and reach the included result. Use representative content to assess labels, navigation and important alternative states. The structure should be understandable to the people approving the work.

03

Creative and interface materials

The agreed identity applications, responsive layouts, component patterns or design files. Include the formats and practical instructions the receiving team needs. Business approval of the offer and content remains separate from approving the visual treatment.

04

Implemented pages and functions

The selected website, store, application or connections, with the stated editor controls and roles. Migration and data preparation have clear boundaries. Review the included task through its result so that a polished screen is accompanied by the behaviour the proposal actually promises.

05

Review and release decisions

A record of the relevant checks, consolidated feedback, unresolved items and release owners. Examine representative phone and desktop journeys where included, along with meaningful failures. Agree launch dependencies and any recovery work before the change reaches ordinary use.

06

Training and ownership information

Demonstrate routine editing or staff work with the intended team. Supply the agreed files, access ownership and support route. Explain ongoing platform charges, care and later improvements separately, so the business can operate the accepted release with a clear understanding of responsibilities.

Optional hypothetical example

A hypothetical example: the contact is arranging a project for someone else.

Imagine a person enquiring about a new website on behalf of another organisation. They can coordinate the conversation and supply a draft brief, while a different person owns the business offer and the future site. A form that assumes the sender is always the business owner may leave the project team with an incomplete account of who the work serves.

The scoping conversation can record the sender's role, the organisation receiving the work and the person authorised to approve public information. Ask which decisions the coordinator can make and who should join later reviews. Collect the context needed for the conversation without asking for account credentials or treating the sender's name as proof of authority.

The proposal and review invitations can then follow that agreed arrangement. This is a hypothetical project example, not a Bristol agency or client engagement. It concerns the participants in a complete website or wider digital commission; it does not prescribe a particular form or require every project to use an intermediary.

Bring the material that makes the brief useful.

Send a useful account of the audience, present website or process and the difficulty prompting the project. Approved service descriptions, brand files and genuine work examples help us discuss the public experience. A representative staff task can be explained with suitable redacted material. Identify who supplies content, who will operate the result and who can approve the important decisions.

If someone is coordinating the project for another organisation, explain that arrangement early. Include the technical account owner when existing tools need inspection. Missing content, an unresolved operating decision or a required supplier can then be recorded as a planning dependency instead of emerging as an unexplained delay during implementation.

Use each stage to settle the next useful decision.

Bristol projects are coordinated remotely from Ranchi through agreed sessions, reviewable material and written feedback.

  1. 01

    01 — Explore the requirement

    Discuss the users and current arrangement with the people who know them. Compare a focused improvement with a broader commission. Establish necessary inputs, decision ownership and the questions affecting the proposed scope and estimate.

  2. 02

    02 — Shape the experience

    Organise information and prepare the selected creative or interface direction. Use representative material to review a complete page or journey. Combine feedback around the same version and resolve the business decisions needed before implementation continues.

  3. 03

    03 — Develop and review

    Build the included functions and content structures, handling retained material and connections within scope. Follow the agreed tasks and suitable exceptions with reviewers. Record corrections and later ideas separately so acceptance remains tied to the commission.

  4. 04

    04 — Publish and transfer

    Confirm content, technical readiness and the receiving responsibilities. Demonstrate a routine update or operating task and deliver the agreed source materials. Record maintenance and future changes as continuing arrangements with an identifiable owner.

Questions before commissioning the project.

Where does the project team work?

Softglimmer's studio is in Ranchi, India. We serve Bristol remotely, agreeing contacts and suitable reviews for the commission. Dated invitations can use Europe/London and Asia/Kolkata, with participants checking the local time for that date. Written decisions help people contribute between sessions. This guide does not represent a Bristol office or imply particular support hours; those arrangements are set in the project plan.

Can you work with material or design prepared by another team?

Yes, subject to the available files, approved uses and the work required to turn them into the agreed result. We review what is supplied and identify any missing content, states or implementation guidance. Your team confirms the facts and ownership of the material. The proposal separates supplied creative work from our design, development and preparation responsibilities, with the handover format agreed before work begins.

Can one project include a website and connected operating work?

It can, when the website journey and operating requirement are understood. We identify the records, access, decisions and external services involved before specifying a connection or application. A public website may also be a complete scope of its own. The estimate describes the selected outputs, review stages, continuing costs and client inputs, while later features remain a separate decision rather than an indefinite promise attached to launch.