SBTEXMEDIA
Premium Creative Studio
Loading Experience...
Employee Surveys ✦ Training Quizzes ✦ Branching Logic ✦ Excel & SharePoint ✦ Power Automate Workflows
"The best form is the one that lands where your team already works — not in another login they'll forget."
SBTEXMEDIA designs professional Microsoft Forms for organisations running on Microsoft 365. Led by Bayazid Kajol, founder of SBTEXMEDIA, this service covers employee surveys, staff onboarding forms, training quizzes, holiday and IT request forms, incident reports, event registrations and customer feedback — together with the Excel workbooks, SharePoint lists and Power Automate workflows that sit behind them.
The reason to choose Microsoft Forms over anything else is rarely the form itself. It is where the form lives. If your organisation already runs on Microsoft 365, a form built here inherits your existing accounts, your access controls, your data residency arrangements and your compliance posture. Responses can restrict themselves to people inside your tenant automatically, capture the respondent's identity without asking for it, and flow into the same Excel and SharePoint your team opens every morning. No new tool, no new login, no procurement conversation.
What most organisations miss is everything after the submit button. Microsoft Forms links to Excel readily, but leaves that workbook raw. It connects to Power Automate, but almost nobody sets up the approval routing, Teams notifications or document generation that would remove the manual step someone currently performs by hand. That downstream work is where the value is, and it is included here rather than treated as a separate project. Where Google Forms or Jotform would genuinely serve you better, I will say so.
Your licence already includes it. What it does not include is anyone designing it properly.
Microsoft Forms arrives bundled with Microsoft 365, which means most organisations acquire it without deciding to. Somebody in HR builds a staff survey, somebody in operations builds a request form, and within a year the tenant contains dozens of forms nobody has audited. Several duplicate each other, most have no branching, almost none validate anything, and the responses feed Excel files that a person tidies before anyone can act on them.
The recurring cost sits in that manual step after submission. An IT request form is submitted; someone checks the responses tab, notices it, decides who should handle it, and forwards it. A holiday request arrives; someone emails a manager for approval, waits, then updates a tracker. Each of these takes only a few minutes, which is exactly why nobody questions them. Across a year and a whole organisation, those few minutes become weeks of salaried time spent moving information between systems that could be connected.
Power Automate exists precisely to remove that step, and it is included in most Microsoft 365 plans your organisation already pays for. A submission can route itself to the correct approver based on the answers, post a card into the relevant Teams channel, create a SharePoint list item, generate a formatted document and email a confirmation — all within seconds and without anyone remembering to look. The capability is sitting unused in the majority of tenants I see.
Data quality is the other silent cost. Without validation and controlled choices, a department name arrives spelled six ways and a date arrives as free text. Nobody can chart that, so the quarterly report gets assembled by hand. Fixing it at the form stage takes minutes; fixing it downstream takes somebody's afternoon, repeatedly, forever.
There is also a governance dimension that matters more in Microsoft environments than elsewhere, because forms built here often touch employee data. Who can view responses, whether submissions are restricted to your organisation, whether identity is captured, how long data is retained, and where it is stored are all configurable — and all frequently left on defaults that nobody has reviewed.
Six outcomes that separate a designed form from one built in a lunch break.
If any of these describe your organisation, this is the service you are looking for.
Twelve-plus sectors, each with its own rules on employee data, record retention and internal access.
Microsoft Forms is disproportionately used for internal processes, which means the data involved is often employee data — and employee data carries obligations that customer feedback does not. Who may view responses, whether identity is captured, how long records are kept and which manager is permitted to see what all vary by sector and jurisdiction. Across the sectors below I have enough working literacy to raise those questions during the brief rather than after an audit.
The same six steps on a five-question pulse survey and a routed approval workflow.
Internal form projects fail in a specific way: the questions get agreed quickly, nobody maps what happens after submission, and the finished form still requires a person to read responses and forward them. I work backwards from that downstream process deliberately, because the automation is usually where most of the value sits.
Six reasons drawn from what returning clients say when I ask them why they came back.
Every Microsoft Forms project includes all of the following — none of it is an upsell.
The questions clients ask before commissioning a form. For broader questions, see the main FAQ page.
Tell me what you need to collect and what currently happens after someone submits. You'll get an honest recommendation, a clear scope and a fixed quote — usually within a few hours, with no obligation attached.
"Let's turn your vision into something exceptional — together."
I respond within a few hours. Tell me what you need to collect.