Proposal · November 2026
A dedicated product designer who owns design at Tenefly, so the two of you can run the pilot and the roadmap. We take the MVP your pilot teachers use today to a V1 you are confident putting in front of the next schools. Before you commit to anything, you see it working on your own product for three days, free.
What you told us
From our call on 4 November. Everything below is how we already work, not something we would set up just for you.
Right now the two of you hear the pilot feedback, set priorities, work with the school and give your engineer design direction. You want that last part to belong to one person.
The rough MVP was enough to sign your first school. Before you bring on more pilot schools early next year, it has to feel like a real product that busy teachers adopt without help.
A trial only tells you something if the designer works on your real product, with your context, the way they would every week after. So ours starts with a kickoff and product access, and the designer who runs it is the designer you keep. We design while you sleep, so each day's work is in your Slack before your morning starts in New York.
Both of you and your engineer. You choose the feature, and we get test accounts, recent pilot feedback and a Slack channel. No feature in mind? We suggest lesson creation, your core loop.
You pick the featureThe designer uses Tenefly the way a teacher would, then audits the chosen flow and lists every colour, font and button style currently in use.
In Slack: Loom + ranked issuesThe redesigned flow mapped end to end, edge cases included, as wireframes. Plus the first version of your shared foundation: type, colour, spacing and core components.
In Slack: flow + wireframesOne or two key screens finished on the new foundation, a handoff note your engineer can build from, and five questions to ask teachers in your next pilot meeting.
In Slack: screens + handoffWe walk you through all of it and share a plan for month one. Then you decide. If you go ahead, the plan starts on Monday 16 November.
Not only one or two screens, but the thinking around them: what is wrong, why it matters to a teacher, the flow that fixes it, and the system that keeps it consistent. It is the same work you would get every week.
A ranked list of what slows a teacher down in the chosen flow, with a Loom that walks through each issue on screen.
Mapped end to end as wireframes, including the empty, error and first-time states that usually get missed.
Type, colour, spacing, buttons, inputs and cards. It answers how long a working system takes: you see the first version on day two.
One or two key screens of the flow, designed on the new foundation, so you can see the quality bar the V1 is held to.
States, spacing and components written up and mapped to Tailwind, so your engineer can build it without guessing.
What we would do next and in what order, plus a five-question teacher check to run in your next pilot meeting.
Relevant work
A product with several kinds of users, each needing their own view of the same system, which is where Tenefly is headed with teachers, co-teachers and school admins.
What clients say
Working together
Your designer works as part of your team. The founders stay on the account, so you always have someone senior to talk to.
Your designer joins your standups and works in your Slack, your Figma and whatever tracker you use. Live where it helps, written updates for the rest.
Yusuf and Maaz guide the designer's work, join a check-in with you every two weeks, and sit in on pilot teacher sessions when it helps.
Annotated Figma files with every state, and components mapped to your Tailwind setup, so nothing is left to interpretation.
A short written note or Loom at the end of each day: what moved, what is next, and anything we need from you.
The same designer, week after week. If that ever has to change, you hear it from us first and the new designer overlaps for a week. Everything lives in your Figma, so nothing is lost.
We sign your NDA, and every designer is covered before they see student data. You own every file from the first delivery.
See it in action
Common questions
Yes. Three working days, Tuesday to Thursday, with no cost and no obligation. All we ask for is a kickoff call and access to the product, because that is what makes the three days worth judging.
More than you might expect, because the first day goes into your real product instead of guesses. By Thursday you have an audit, a redesigned flow, a starting design system, one or two finished screens and a handoff note for your engineer.
The basics (type, colour, spacing and core components) take three to four days, and you see the first version on day two of the trial. After that it grows with every feature we design, rather than being a separate project your roadmap waits on.
The plan is a flat monthly fee for half-time capacity, so there are no timesheets to check. You see the work itself: a daily update, the files in your Figma, and a check-in every two weeks to look at what shipped and what comes next.
Your designer. For the first two weeks Yusuf joins as well, while the foundation and the way we work together are being set up.
Everything, from the first delivery: the Figma files, the design system and every asset. If you ever stop, you keep all of it.
Investment
Start with three free days. The plan only starts if the trial works for you.
All prices in USD. Plans change only with your sign-off.
Ready when you are
Reply with the feature you want us on and we will book Monday's kickoff. Not sure which one? We will suggest it.