From an idea to something real, with someone alongside you.

A decision to make, systems to connect, or a team that wants to work better with AI? Let’s start with the need and agree on a useful way forward.

Based in Saguenay · French & English · Remote worldwide · Travel by arrangement

Tell me what you’re working on

An idea, a problem… or both?

I'm Keven. I've worked in software for more than 15 years. I've built websites, online stores and applications for businesses, and worked with development teams of different sizes.

I like understanding what people are really trying to do, explaining the options and getting hands-on. I can help you make a decision, but also build, test or unblock something concrete. Software, guidance and AI belong in the same toolbox; the problem determines what is useful.

A few things to look at

  1. k11e / Keven LefebvreSince 2008Consulting · Development · Workshops
  2. Shopify2021–presentSenior software development
  3. Turbulent2020–2021Technical leadership · core team
  4. Arsenal Web / Polka2018–2020Consulting and fractional technology leadership
  5. OrbiteWeb2008–2018Founder · custom development

Organizations and projects

  • GardaWorld
  • IAMGOLD
  • TFO
  • GHD
  • Ville de Saguenay
  • UQAC
Across engagements carried out directly or as part of teams and agencies.

What we can work on together

Understand and decide

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. The client studies a tangled wall shadow as three suspended objects sway with their gestures. Kev and the client each draw an object aside; the shadows become distinct. The client points to an area and Kev adjusts the light. All elements remain present. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Make sense of the options

Choosing between tools? Received a proposal and wondering what it actually means? I can look at the situation with you, compare the options and help you prepare the right questions before you decide.

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. The client pulls a roll bearing their sketch, hesitates at the blank paper unfurling, then lets it curl back. Kev holds the paper as they fold the surplus into an accordion. They draw three stages, split the oversized one in two and circle the first. The client puts a finger on it. The whole idea remains. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Make a plan

Have an idea but no plan yet? We can clarify the problem, who it affects and what would be useful first. The goal is to find a starting point and next steps that fit your constraints.

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. The client and their counterpart show different drawings in speech bubbles without understanding one another. Kev places a shared board: the client draws the desired result, the counterpart adds technical parts and Kev links them. The client requests a change; the counterpart adjusts the diagram. Kev steps back as the two exchange directly. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Bridge the gap

Technology doesn't have to be your first language. I can help you explain what you need, talk with a team or vendor and understand the choices being presented. The point is for you to be able to take part in decisions about your project.

Build and get unstuck

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. The client tries incompatible plugs from two nearby boxes. Kev examines them and assembles an intermediate module while the client holds the plugs. He adjusts it with a tool and they connect both ends. The client activates one box; a blue element crosses the connection and the second box responds. The client then repeats the test independently. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Build and connect

A prototype, a feature, an internal tool or two systems that need to exchange information: I can help with the development. AI and automation can be part of the solution when they're useful, but they aren't mandatory.

Not necessarily starting from scratch.

You have done something similar before, but nobody can find the right file? We can explore how to make that work reusable instead of starting again.

Activate the file drawing to play a short animation within the text. Use the same drawing to replay it.
A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. Kev starts untangling the cord, then the client understands and takes the free end to finish together. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Get unstuck

Has your project slowed down, or is your team stuck on a technical problem? I can bring an outside perspective, help understand the blockage and work on a defined piece of it. We'll agree on the scope before starting; I won't promise a solution before understanding the problem.

Understand the blockage. Agree on the scope before starting.

A practical experiment

AI in your day-to-day work

An interesting demo is not yet a working process. If you have a repetitive task, documents to work through or an automation idea, we can look at how things happen now and what is worth trying. AI might help; a simpler tool might be the better choice.

  • Find a starting point. Examine the need, available tools, data and what would make a result useful.
  • Try a real, bounded case. Build a prototype, small automation or experiment that can be compared with the way you work today.
  • Decide what to keep. Check errors and difficult cases, document what works, then decide whether to continue, adjust or stop.

That can be a working session, a guided experiment or a small development engagement. You do not need to buy a large project to examine an idea.

Data and human review

Help a team progress

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. Two colleagues hold a frame that racks and take turns compensating. Kev supports it, shows one colleague how to fasten the first bracket, then passes over the tool. The colleagues repeat the technique on the second bracket. Kev starts to help, sees they can manage and lowers his hand. They release and push the frame: it stays stable. They continue without needing Kev to hold it. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

Support a team

I can work alongside developers, share knowledge or lead a practical session around a real problem. I can also provide part-time technical direction: review an architecture, help make a decision or support the team for a defined period. For AI-assisted development, we can build a workshop around your work.

A hands-on workshop

Practice AI with your development team

Already using coding assistants, or want to try them without confusing speed with quality? We can prepare a practical workshop around a representative development task. The point is not to memorize magic prompts, but to know what to ask, what to check and when to take over.

We can work in your repository if access and tool-use permissions allow it, or prepare an example without confidential code or data. A session can follow a change from beginning to end:

  1. Read the context and frame a task precisely enough to evaluate its result.
  2. Produce a small change with the assistant, then inspect the code and proposed choices.
  3. Test the important cases, look for mistakes and review what remains uncertain.
  4. Document the change and checks the team can repeat without me.

The aim is to leave with an annotated example, reusable checks and working practices that fit your team. We agree on the artifacts, starting level, duration and format together, before the session.

I enjoy teaching while building with people. My career story includes supporting developers as we learned a new stack together. Trying things, explaining the choices and leaving people better equipped for what comes next: that is the way I want to work with your team.

Working together

Who is this for?

Entrepreneurs, businesses, teams and individuals with a project who are ready to invest time and resources in it. You don't need all the answers—or the name of the right tool—before writing to me. Curiosity, context and a willingness to work together are a good start.

Keep judgment and data in the right places

AI can be wrong, inconsistent or unsuitable for a task. A person remains responsible for reviewing the result, especially when it informs an important decision. We agree on checks before treating a convincing output as a good answer.

Some tools send code or information to outside providers. We discuss permissions, data sensitivity and tool choices before using them. Please do not send confidential information in your first email.

An engagement that makes sense for you

A brief glance greets the cursor when it enters the drawing, then eyes return to the task. The crosshair appears on entry; click once to bring Kev in from that point. An enormous toolbox sits beside a small loose lamp. Keven examines the joint, opens the box and chooses one small screwdriver. The client holds the lamp while he tightens one screw. The client switches it on and checks that it stays steady. The larger tools remain in the box; the small tool was enough. Click in the drawing to pause or resume. While paused, eyes follow the cursor and all work stays still. Touch or keyboard activation brings Kev in directly. Links and surrounding text keep their normal behavior.

A working session, a few hours to examine a question, a team workshop, a short contract or part-time support: we can choose the format that fits the problem. Your first email gives me context so I can suggest an approach. Before work begins, we agree on the goal, what is included, the cost and a time or budget cap. We also agree on access, communication and handoff. If going further makes sense, we can discuss that separately.

A note

Want to talk?

Email me directly. A few lines about what you have in mind are enough to start. No form to fill out.

kev@k11e.com
Image viewer