Tools for teams
Notifly
Connect customer information, marketing and automation. A systems challenge where information and actions need to work together.
Explore at notifly.vn (opens a new tab)
Building digital products.
Starting with people.
1997 Studio designs and develops websites, apps and business software. Together, we turn what you have in mind into a product people can use and operate.
Good looks are a start.
Usability takes it further.
A digital product matters when it helps someone get something done. We think beyond screens to the people, content and interactions that make up everyday use.
From the first sketch to handover, Studio helps you clarify what to build, try how it works and agree on each part of the work. Design and development belong to the same process.
- 01
Understand the problem
Start with goals and context to identify what needs to be solved.
- 02
Decide together
Review designs, consider options and define scope before development.
- 03
Think beyond launch
Plan for content, administration and everyday use after handover.
We don't just talk about products.
We build our own.
Notifly and Todomi are products by 1997 Studio. Explore them directly to get a better sense of our approach to design and development.
Tools for individuals
Todomi
A place to capture and organise personal tasks. An experience designed around simple actions in everyday life.
View Todomi on the App Store (opens a new tab)
Illustrations, not interface screenshots. Find current product information through the links above.
Clear at every step.
All the way to handover.
Know what Studio is doing, where your input matters and what needs approval. Open each step to see how we collaborate.
This is a reference process for a full-scope project. Steps may be combined or adapted for each service; scope, update schedules and support are confirmed in the project agreement.
01
Listen and clarify your needsUnderstand the problem before choosing a solution.Studio's part
Discuss goals, users, current operations and the points that get in the way. Record open questions instead of rushing to settle features.
Your part
Share your needs, existing content, references and preferred timing. A complete brief is not required to start.
Ready to move forward
A summary of needs and priorities so both sides can confirm they understand the same problem.
02
Agree on scope and a planClarify work, costs and responsibilities before starting.Studio's part
Propose tasks, deliverables, costs and estimated milestones. Clarify exclusions, revision rounds, acceptance criteria and support conditions.
Your part
Review the proposal, name an approver and agree when content will be provided. Discuss budget or timing limits from the start.
Ready to move forward
Scope and terms are confirmed, and the agreed starting conditions are met before development.
03
Structure content and user flowsKnow where people go, what they do and what they get.Studio's part
Sketch the site structure, information order and main flows. For complex products, use wireframes or prototypes to review how they work together.
Your part
Check content and business requirements for accuracy, and add real situations your users commonly face.
Ready to move forward
Approved structure and main flows, with a list of content still to prepare.
04
Design and refine togetherReview concrete designs before development.Studio's part
Design interfaces around your brand and the agreed structure. Present screens, states and layouts for devices within scope.
Your part
Consolidate feedback for each round and explain what does not fit and why. The named approver confirms the direction to avoid conflicting decisions.
Ready to move forward
An approved design that becomes the basis for development. New requests are reassessed if they change the scope.
05
Develop and share progressSee the product take shape in a working preview.Studio's part
Build the agreed features and integrations. Share completed work, work in progress, issues requiring input and previews at project milestones.
Your part
Provide content and necessary access through suitable channels. Review previews and give feedback on business requirements.
Ready to move forward
A working preview covering the agreed scope, with a list of issues to resolve before acceptance.
06
Test and approveCheck quality against specific criteria.Studio's part
Check main flows, forms, links, error states and layouts on agreed devices and browsers. Record and fix in-scope issues, then test again.
Your part
Try realistic scenarios against the acceptance criteria. Confirm the result or describe what needs further work.
Ready to move forward
Test results and acceptance items are confirmed. Any outstanding items are recorded with an agreed resolution.
07
Launch and hand overReceive the product and learn how to manage it.Studio's part
Coordinate launch according to the plan. Hand over agreed accounts, documentation and assets, and explain essential operating tasks.
Your part
Name the person taking over, check their access and try tasks such as updating content or reviewing enquiries.
Ready to move forward
The handover checklist is checked. The person responsible knows how to use the product and where to get help.
08
Support and improveHave a clear contact for questions, issues and future work.Studio's part
Receive questions, provide guidance and classify issues. Distinguish covered issues from new requests, and discuss the approach and estimated timing under the agreement.
Your part
Share descriptions, screenshots or reproduction steps through the agreed channel. For new needs, explain your goals so we can prioritise together.
Ready to move forward
Know how your request is being handled. Additional development begins only after both sides agree on scope, costs and a plan.
Something changed? Let's clarify it first.
Record the request → assess the impact → confirm the change → then implement. Any change of plan should include a clear explanation, affected work and next steps.
Aligned in how we think.
Clear in how we work.
Studio could be a good fit if…
- You have a problem to solve, not just an interface to refresh.
- You want design to connect with development and real-world use.
- You are ready to review, give feedback and prioritise within your project's scope.
And some things need to be clear from the start.
An initial conversation is not a commitment on price or timing. Features, revision rounds, asset ownership and post-handover support should be specified in the agreement. Requests outside the scope need to be discussed before work begins.
Before placing your trust,
ask what you need to know.
Questions worth asking in the first conversation.
[email protected]How do we start without a complete brief?
Tell us what you want to do, who will use it and what problem you face. Content, images or reference websites can help make the conversation more specific. You do not need to choose a technology first.
Can we hire you for design or development only?
Studio offers UI/UX design, websites, business software and mobile apps. If you need only one part, share your existing materials so we can define our work and the handoff with your team.
What if something changes during the project?
It helps to distinguish in-scope revisions from additional requests. Both sides should clarify the impact on work, cost and timing before proceeding. Revision rounds and approvals are agreed per project.
Who manages and supports the product after handover?
Ownership of administration, access rights, documentation and support scope should be stated in the agreement. We also identify third-party services and operating costs you will need to manage.
Are the images on this website client projects?
The drawings illustrate our services and working process. Design explorations are not evidence of delivered client projects. Explore our own products through the Notifly and Todomi links above.