Our behavioural framework
How we study present bias in saving, run experiments, and turn messy behaviour into simple prompts, rules, and tables you can actually use.
How we study present bias in saving, run experiments, and turn messy behaviour into simple prompts, rules, and tables you can actually use.
We begin by reviewing behavioural finance and psychology research on present bias, time inconsistency, and related concepts. Our team maps key findings into simple patterns, then checks them against real life in India, including irregular income, festivals, and family pressures, to see which ideas matter most for everyday saving decisions.
Using those patterns, we design lightweight tools such as prompts, rules, and comparison tables. Each tool targets a specific decision point, aims to be usable in minutes on a phone, and is written in plain language so it can be adapted to different financial setups and personal constraints.
After each test, we analyse patterns in use, drop tools that create friction, and refine language or timing for those that show promise. We document both successes and failures, and we explicitly state that past performance does not guarantee future results, and that results may vary by person and context.
Build a living system that evolves with you
Traditional advice assumes discipline. Our framework assumes present bias, limited attention, and noisy lives, then builds around those constraints instead of denying them.
Old approaches to saving told people to “be disciplined” and assume a straight line from intention to action. Our methodology starts from a less flattering but more accurate view: present bias is strong, attention is limited, and life in India is noisy. We build and test small behavioural tweaks that work with these constraints, then keep only those that still function when motivation drops and days get messy. Results may vary for each person.
Experiment then refine
We run small experiments, compare options side by side, and keep what works in messy real life, not just what sounds elegant in theory or slides.
Systems, not slogans
We focus on automatic rules, prompts, and checklists that fire at the right time, reducing the need for constant self control or detailed planning.
We track behaviour in weeks and months, not hours, so we see whether small changes actually survive stress, festivals, and shifting incomes.
We built our approach by borrowing from behavioural finance, psychology, and field research, then stripping out jargon until only practical steps remained. The goal is simple: help people in India see where present bias tilts their saving decisions, and offer small, testable tools that can survive real life without promising any specific outcome. Below is how we turn research into something you can actually use.
We start with peer reviewed work on present bias, time inconsistency, and related concepts from behavioural finance and psychology. Our team then cross checks those ideas against local realities in India, such as irregular income, festival seasons, and family expectations. Instead of copying experiments directly, we translate them into plain language patterns and ask a simple question: where does this show up in everyday saving decisions.
We run structured interviews and surveys with volunteers who are willing to talk through their actual saving history, not just ideal plans. We look for gaps between what they said they would do and what they actually did at key moments, such as salary day or big sales. These stories reveal how present bias, stress, and social pressure interact, and they give us concrete decision points to target with prompts or rules.
For each pattern we identify, we design small tools: short checklists, automatic style rules, and simple comparison tables. We test them with volunteers over several weeks, tracking how often they are used, when they are ignored, and whether they reduce regret or last minute stress. Tools that demand too much effort or attention get cut or simplified, no matter how clever they looked on paper.
We then document what worked, what failed, and where results were mixed. Instead of hiding messy outcomes, we surface them in case style stories and notes on limitations. We remind users that past performance does not guarantee future results, and that results may vary based on context, motivation, and external events they cannot control.
Turned into usable flows
Finally, we package the surviving tools into clear flows: map your patterns, pick one rule, run a short experiment, review, and adjust. This keeps the methodology accessible without turning it into a rigid programme. You can use parts of it alone or bring the structures into conversations with trusted professionals who know your full situation.