Shared inboxes
Categorise incoming messages, route them appropriately and prepare staff-ready draft responses.
Early-stage startup · Practical AI · Controlled delivery
Turn repetitive work into a controlled, practical workflow.
JSR Growth Lab is an early-stage workflow automation startup helping education providers, professional services and other information-heavy organisations examine repetitive work, design practical staff-support tools and evaluate solutions through small, controlled and measurable pilots.
We begin with one workflow, one team and one clear operational result—while keeping staff in control of decisions and external communications.
Initial discussions are exploratory and carry no obligation to proceed.
Problem firstWorkflow before technology
Focused scopeOne measurable use case
Human controlStaff retain responsibility
Honest evaluationResults and limitations documented
The problem we address
Your organisation may not need “AI transformation.” It may need one process fixed.
Organisations often lose time to repeated enquiries, manual data entry, document searching, meeting follow-ups, record checking, workflow coordination and routine reporting.
Document searching
Retrieve relevant information from approved policies, procedures, guidance and knowledge sources.
Meeting follow-ups
Convert approved notes into summaries, actions, ownership, deadlines and follow-up drafts.
Record checking
Identify missing, inconsistent or duplicate information for staff investigation and correction.
Workflow tracking
Monitor outstanding tasks, approvals, customer follow-ups, deadlines and required information.
Routine reporting
Prepare structured operational summaries and management information for staff review.
Not every workflow requires generative AI
Depending on the problem, an appropriate solution may combine process redesign, rules-based automation, forms, integrations, dashboards, search or AI-assisted drafting. The objective is a practical and controlled improvement—not the use of AI for its own sake.
Solutions
Discovery-led workflow improvement
We examine the current process, identify tasks suitable and unsuitable for automation, and shape a focused solution around the organisation’s information, users, controls and desired outcome.
Education, training and membership organisations
Workflow support for organisations managing high volumes of enquiries, documents, applications and stakeholder communications.
- Enquiry categorisation and routing
- Approved policy and knowledge search
- Applicant, learner or member communication drafts
- Meeting and follow-up administration
- Event and engagement tracking
- Operational reporting and record-quality checks
Professional and business services
Practical workflow support for organisations relying on documents, repeated communication and manual coordination.
- Shared-inbox triage
- Client onboarding workflows
- Document search and summarisation
- Meeting and action management
- CRM follow-up workflows
- Proposal, report and management-summary preparation
Bespoke workflow discovery
If the right solution is not yet clear, we examine the process before recommending a tool.
- Current workflow and principal bottleneck
- Suitable and unsuitable automation tasks
- Proposed solution and expected outputs
- Human review and required safeguards
- Data and integration considerations
- Measurable pilot outcomes and delivery stages
Suitable organisations
Where information and follow-up create operational friction
JSR Growth Lab is particularly interested in organisations where staff handle high volumes of information, repeated communication, documents, follow-ups or manual reporting.
Potential organisations
- Universities, colleges and training providers
- Professional-services businesses
- Recruitment and employment agencies
- Membership bodies and associations
- Charities and social enterprises
- Property and facilities-management companies
- Consultancies and project-based businesses
- Growing organisations using shared inboxes and spreadsheets
What determines suitability?
Suitability depends on the workflow, information involved, required judgement, existing systems and organisational controls—not simply the industry.
A suitable first project normally involves a clearly understood, lower-risk internal process with measurable outputs and meaningful staff review.
What makes a good first workflow?
A useful starting point is normally:
- Repeated frequently
- Handled through email, documents or spreadsheets
- Time-consuming but reasonably well understood
- Measurable in time, quality or response speed
- Suitable for staff review before action is taken
- Demonstrable with synthetic or non-sensitive information
Start carefully
Choose a workflow that can be tested without disrupting critical operations
Highly sensitive, poorly defined or high-impact decision-making processes are unlikely to be appropriate starting points.
The purpose of discovery is not only to identify where automation may help. It is also to identify what should remain manual, what requires professional judgement and which controls are necessary before any pilot.
Pilot process
Start with a focused, low-risk pilot
A typical engagement begins with a small workflow that can be examined and tested before any wider deployment is considered.
Discovery
Understand the process, users, volumes, delays, decision points, existing systems and desired result.
Pilot concept
Define the use case, exclusions, outputs, safeguards, inputs, success measures and what should not be automated.
Demonstration
Where appropriate, create an early demonstration using approved public, fictional, anonymised or non-sensitive information.
Controlled pilot
Test with a limited group, agreed controls, clear escalation rules and staff review of important outputs.
Evaluation
Document results, limitations, corrections, user feedback and options before considering a wider rollout.
Illustrative concept
Example pilot: Meeting-Action and Follow-Up Copilot
This is an exploratory example—not a claim that every organisation needs the same tool or that the concept has already been deployed for a client.
Potential problem
Staff can spend time converting meeting notes into actions, follow-up communications and activity records. Important actions may also remain incomplete when ownership, deadlines or missing information are unclear.
Potential input
Synthetic, public, anonymised or otherwise approved non-sensitive meeting notes during the initial demonstration.
Possible uses
Client meetings
Supplier discussions
Recruitment meetings
Project reviews
Partner engagement
Internal operations
Draft outputs
- Concise meeting summary
- Proposed actions, owners and target dates
- Missing-information checklist
- Staff-ready follow-up email draft
- Structured activity record
- Summary of open or overdue actions
Human control
Nothing would be sent externally or entered into another system until reviewed, edited and approved by an authorised member of staff.
Possible evaluation measures
- Time required to prepare actions and a follow-up draft
- Percentage of actions accurately captured
- Staff corrections required before approval
- Incomplete or overdue actions identified
- Staff assessment of usefulness and ease of use
Responsible AI
Practical automation with clear boundaries
JSR Growth Lab advocates human-in-the-loop design for important, sensitive or regulated work and initially prioritises staff-support and administrative workflows rather than autonomous decision-making.
Pilot principles
- Begin with a clearly defined operational problem
- Use approved information sources
- Minimise personal and sensitive information
- Use synthetic or anonymised information where practical
- Keep staff responsible for important decisions and communications
- Provide escalation routes for uncertain or sensitive cases
- Test accuracy and limitations before wider use
- Document responsibilities, controls and success measures
Not a route to unaccountable automated decisions
We do not propose automating high-impact decisions involving employment, education, finance, healthcare, legal rights, immigration, safeguarding or access to essential services without appropriate governance, qualified professional oversight and accountable human decision-making.
Information use
Client information would not be used to train a general-purpose model unless explicitly approved and contractually agreed. Any production approach would require appropriate review of hosting, providers, access, retention, security and data-protection responsibilities.
Delivery model
View
technical capability
Discovery-led, with specialist engineering support when required
JSR Growth Lab leads early-stage workflow discovery, requirements analysis, solution design and pilot coordination. Where specialist development, integration, deployment or technical support is required, delivery may be provided through an independent engineering partner such as GammaEdge, subject to client approval, technical due diligence and separately agreed scope and commercial terms.
Jyotsana Singh Rajawat
Founder, JSR Growth Lab
MSc Artificial Intelligence
MBA with Distinction
About the founder
Connecting operational challenges with practical AI solutions
Jyotsana is the founder of JSR Growth Lab, an early-stage workflow automation startup, and is completing an MSc in Artificial Intelligence at the University of Surrey.
Her focus is the practical application of AI and automation to operational problems: understanding how work is currently performed, identifying appropriate opportunities for improvement and shaping controlled pilots with clear human oversight.
She also holds an MBA with Distinction and combines business analysis and stakeholder communication with postgraduate study in artificial intelligence. JSR Growth Lab connects organisations facing operational challenges with structured workflow discovery, practical solution design and appropriate technical delivery capability.
Why JSR Growth Lab?
A focused bridge between operational need and appropriate delivery
Problem first
We start with the process, bottleneck and desired result—not a fashionable or predetermined tool.
Focused scope
The first engagement centres on one clearly defined workflow with realistic exclusions.
Human control
Staff remain responsible for important decisions, commitments and external communications.
Measured outcomes
Pilots use agreed measures such as time, accuracy, corrections, completeness or user feedback.
Appropriate delivery
Specialist engineering capability can be introduced when justified by the project requirements.
Honest limitations
We distinguish exploratory concepts, demonstrations, controlled pilots and production-ready systems.
Frequently asked questions
Questions before starting
Do we need to know exactly what tool we want?
No. A discovery conversation can begin with the current workflow, the main difficulty and the result you want. The suitable approach may involve process redesign, conventional automation, integrations, search or AI-assisted work.
Does the first discussion require a commitment?
No. The initial conversation is exploratory. If an appropriate opportunity is identified, the next step may be a short workflow assessment or one-page concept, with each later stage considered separately.
Will a pilot require access to live systems?
Not necessarily. An initial demonstration can often use synthetic, public, anonymised or otherwise approved non-sensitive information. Live integration would require separate technical, security, governance and data-protection review.
Will the tool communicate or make decisions automatically?
Not by default. Controlled pilots can keep outputs as drafts for staff review. The required approval and escalation rules should be defined for the specific workflow.
Can JSR Growth Lab support organisations outside education?
Yes. The approach is relevant to information-heavy organisations that rely on documents, repeated communications, manual coordination and reporting. Suitability depends on the workflow and risk—not simply the sector.
Who provides the technical implementation?
JSR Growth Lab leads discovery, requirements and solution design. If specialist development, integration, deployment or technical support is required, an independent engineering partner may be introduced subject to client approval and separately agreed terms.
Are cost or efficiency benefits guaranteed?
No. Benefits should not be assumed before the current workflow and baseline have been understood. A controlled pilot is used to test usefulness, accuracy, limitations and measurable outcomes.
Contact
Start with one time-consuming process
Describe the workflow, where time is being lost and what a useful improvement would look like. Please do not submit confidential, personal or sensitive information through this form.
Privacy notice
How enquiry information is handled
Last updated: 18 September 2026
Who is responsible for the information?
JSR Growth Lab is responsible for the personal information submitted through this website or sent to contact@jsrgrowthlab.com. For privacy questions or requests, use that email address.
What information may be collected?
This may include your name, work email address, organisation, team or role, your preferred next step and the high-level workflow information you choose to provide. Basic technical information may also be processed by the website hosting provider to deliver and secure the website.
Why is the information used?
Information is used to respond to enquiries, assess whether a potential workflow opportunity may be suitable, arrange discussions, maintain relevant business correspondence and protect the website from misuse. Depending on the circumstances, processing may be necessary to respond to your request or may be based on legitimate interests in managing relevant business enquiries.
What should not be submitted?
Please do not submit passwords, financial information, identification documents, health information, sensitive employment information, student records, client files or other confidential, special-category or highly sensitive personal information through the website form.
Who may receive the information?
Information may be processed by service providers used for website hosting, form handling and business email. It will not be sold. A potential engineering delivery partner will not receive your enquiry details unless this is necessary, appropriate and explained as part of progressing a relevant opportunity.
How long is information retained?
Enquiry information will be retained only for as long as reasonably necessary to respond, consider the opportunity, maintain relevant business records and meet legal or operational requirements. Information that is no longer required will be deleted or securely disposed of.
Your rights
Depending on applicable data-protection law, you may have rights relating to access, correction, deletion, restriction, objection and data portability. You may also complain to the UK Information Commissioner’s Office. Contact JSR Growth Lab first at contact@jsrgrowthlab.com if you wish to raise a privacy question or exercise a right.
International processing
Some technology providers may process information outside the United Kingdom. Where relevant, the applicable provider arrangements and safeguards should be reviewed. This notice will be updated if the website’s services or information-handling practices materially change.